Lyris User's Guide
[previous] [next] [contents]
Starting Lyris
Table of Contents
Introduction
Lyris Email Commands
Web Interface for Users
Server Administrator
Site Administrator
List Administrator
Other Topics
Security Considerations
Security Issues Relating to Members
Lyris Mail Merge
The Lyris command line
Starting Lyris
Database Operations
Setting Server Options
Windows Services
Unix Daemon Option
Modifying lyris.plc
Add-On Packages
Installing and Upgrading
Appendix
Frequently Asked Questions

Starting Lyris

To run the Lyris server, you simply type "lyris start" on the command line. Lyris with no command line parameters will display the available options and then exit.

The "start" action can be modified with a number of options. The options can be anywhere on the command line, in any order. The options are:

debug
Run Lyris Server and display debugging information while running.

If you are running Lyris in the foreground, you can toggle debug mode on or off without restarting the server.

On Windows, you can do this by pressing the ctrl-break key.

On Unix, you can do this by sending a USR1 signal to the Lyris process, which you can do with the command: kill -USR1 `cat /etc/lyris.pid`

threadtrack
When you start Lyris in the foreground with the "threadtrack" option on the command line, Lyris will keep track of the current state of every SMTP mail thread. You can view the instant status of all mail sending threads from the server statistics page, where this additional information is appended. This can be informative, and useful in determining what the Lyris SMTP delivery engine is doing.

nomail
Run Lyris but do not send any mail.

For example, to start Lyris in "debug" mode with no outgoing mail, you would use the command:

    lyris start debug nomail

noscreen
Run Lyris with no screen output

nolcp
Run Lyris with no Lyris Command Protocol service (which runs on port 2020). The Lyris web interface will not be able to communicate with the Lyris server.

lcpconsole
Run Lyris and also display Lyris Command Protocol console. The console allows the user to directly type commands at the terminal, rather than having to connect via port 2020. Among other things, the console allows the terminal user to shutdown the Lyris server.

noincoming
Run Lyris but do not run the incoming mail processing service. Incoming mail will not be processed.

noindexer
Run Lyris, but do not run the full text indexing service. Messages waiting to be full text indexed will not be indexed.

mailtest
Run Lyris, do not actually deliver any email. Lyris will run completely as normal, but during the SMTP transaction will send a RESET and QUIT command right before it is supposed to send the DATA command. This option can be useful to test the load-capacity and stability of a Lyris installation.

nosmtpserver
Run Lyris, but do not run the smtp server which receives mail. No incoming mail will be accepted.

nonntpserver
Run Lyris, but do not run the nntp server which allows Newsgroup access to the Lyris mailing lists.

noscheduler
Run Lyris, but do not run the scheduled task manager. Tasks such as digests will not be run.

nocheck
Run Lyris Server, but do not check for any TCP/IP conflicts. When Lyris starts up, it first checks to see if any other programs are using the TCP/IP addresses and ports that Lyris will need to use. Lyris does this by trying to connect to port 25 (SMTP mail) and port 2020 (Lyris LCP) on all TCP/IP addresses of the machine, or just the TCP/IP addresses Lyris has been configured to use, if the "Multiple TCP/IP Addresses" setting has been used. If one of the ports Lyris needs is being used, Lyris will display and error message and not load. If you prefer, you can bypass this test with the nocheck option, and Lyris will start a few seconds faster.

Other pages which link to this page:
  • Statistics
  • The Lyris command line
  • New in release version v3.0
  • Page 408 of 556