|-h, --help||Prints a brief help message and terminates execution|
|Prints Cherokees version and terminates execution|
|-t, --test||Perform a sanity check on the configuration file. The server will not run.|
|Launches the server as a background process (default behaviour is to stay attached to the controlling terminal).|
|Specifies an alternative path for the configuration file to use instead of the default cherokee.conf|
|-p<PORT>, --port=<PORT>||TCP port number to which the server will listen.|
|Launches a server exposing statically the specified directory. When launched with -r, the configuration file is ignored, and the Cherokee instance runs with its default values.|
|Print server technical information.|
|Execute the worker process under Valgrind. Used only for development and troubleshooting purposes.|
The following signals are supported by Cherokee:
SIGHUP, Restarts the server gracefully
SIGUSR1, Restarts the server closing all the opened connections
SIGUSR2, Reopens the log files
I would appreciate hearing of any problems you have with Cherokee. I would also like to hear from you if you have successfully used Cherokee, especially if you are using it for a distribution.
Report bugs to http://bugs.cherokee-project.com
There is a mailing list for discussion among Cherokee users and for announcements of new and test versions. To join, send a message to firstname.lastname@example.org with the line:
in the body of the message. The submission address is email@example.com.
Cherokee can be run either with this command or cherokee-worker(1). This last option is discouraged if you are not developing though. Note that, for most systems, a startup/shutdown script such as /etc/init.d/cherokee is provided and will probably be the most convenient invocation method.
Alvaro Lopez Ortega <firstname.lastname@example.org>.
This manpage is maintainted by Taher Shihadeh <email@example.com>.
|-->||CHEROKEE (1)||February 16, 2011|