Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

lighty-enable-mod(1) [debian man page]

LIGHTYENABLEMOD(1)					      General Commands Manual						LIGHTYENABLEMOD(1)

NAME
lighty-enable-mod, lighty-disable-mod - enable or disable configuration in lighttpd server SYNOPSIS
lighty-enable-mod [module] lighty-disable-mod [module] DESCRIPTION
This manual page documents briefly the lighty-enable-mod and lighty-disable-mod commands. lighty-enable-mod and lighty-disable-mod are programs that enable (and respectively disable) the specified configuration file within lighttpd configuration. Both programs can be run interactively or from command line. If either program is called without any arguments, an input prompt is dis- played to the user, where he might choose among available lighttpd modules. Immediate action is taken, if a module name was given on the command line. EXIT STATUS Both programs indicate failure in their exit status. lighty-enable-mod or lighty-disable-mod respectively may leave execution with one of the following exit codes: 0 denotes success 1 denotes a fatal error (e.g., a module could not be enabled, or a dependency was not found) 2 denotes a minor flaw (e.g., a module was not enabled because it was already loaded before) Note You can (un-) load several modules at time. The exit status will only reflect the most serious issue (where a minor flaw beats no error, but a fatal error beats a minor flaw). This means, if a minor flaw was encountered as well as a fatal error, the program will leave with exit status 1 and stop immediately. DEPENDENCIES
Debian allows lighttpd modules to formulate dependencies to other modules they depend on. Configuration files are scanned for dependencies upon load or unload of modules, not at runtime of the web server. Such a magic line has the following format: # -*- depends: module[, module] -*- and may appear anywhere in the file. If such a line is found, the extracted name is interpreted as dependency to another lighttpd module. lighty-enable-mod will seek available configurations to satisfy this dependency and will recursively enable all dependencies found on its way. lighty-disable-mod will disable reverse dependencies recursively. SEE ALSO
lighttpd(1) AUTHOR
Program and man pages were originally written by Krzysztof Krzyaniak <eloy@debian.org> and later modified by Arno Toll <debian@toell.net> 2006-01-11 LIGHTYENABLEMOD(1)

Check Out this Related Man Page

strace(1M)																strace(1M)

NAME
strace - write STREAMS event trace messages to standard output SYNOPSIS
mod sub pri DESCRIPTION
gets STREAMS event trace messages from STREAMS drivers and modules via the STREAMS log driver and writes these messages to standard output. By default, without arguments writes all STREAMS trace messages from all drivers and modules. with command-line arguments limits the trace messages received. The arguments, which must be specified in groups of three, are: mod Specifies the STREAMS module identification number from the streamtab entry. sub Specifies a subidentification number (often corresponding to a minor device). pri Specifies a tracing priority level. gets messages of a level equal to or less than the value specified by pri. Only posi- tive integer values are allowed. The value can be used for any argument in the command line to indicate that there are no restrictions for that argument. Multiple sets of the three arguments can be specified to obtain the messages from more than one driver or module. Only one process can open the STREAMS log driver at a time. When is invoked, the log driver compares the sets of command line arguments with actual trace messages, returning only messages that sat- isfy the specified criteria. STREAMS event trace messages have the following format: seq time tick pri ind mod sub text Components are interpreted as follows: seq Trace event sequence number. time Time the message was sent expressed in hh:mm:ss. tick Time the message was sent expressed in machine ticks since the last boot. pri Tracing priority level as defined by the STREAMS driver or module that originates the messages. ind Can be any combination of the following three message indicators: The message has also been saved in the error log. The message signaled a fatal error. The message has also been mailed to the system administrator. mod Module identification number of the trace message source. sub Subidentification number of the trace message source. text Trace message text. runs until terminated by the user. EXAMPLES
Display all trace messages received from the driver or module identified by mod Display trace messages of any tracing priority level from the driver or module identified by mod and its minor devices identified by the sub or Display the trace messages from the same driver or module and subs but limit the priority levels to 0 for subs 2 and 3; 1 for sub 4, driver or module WARNINGS
Running with several sets of arguments can impair STREAMS performance, particularly for those modules and drivers that are sending the mes- sages. Also be aware that may not be able to handle a large number of messages. If drivers and modules return messages to too quickly, some may be lost. FILES
NLS catalog for SEE ALSO
strclean(1M), strerr(1M), strlog(7). strace(1M)
Man Page