Joachim Wiberg
7d09e34b80
* src/pid.c: note the stale-pidfile-cleanup exception to the documented "Finit does not touch pid:! pidfiles" rule. * doc/config/services.md: add a user-facing paragraph on the same. * doc/ChangeLog.md: add Unreleased section covering this PR -- stale pidfile cleanup, restart log with signal name and core dump flag, and the SIGUNKOWN typo fix. Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
This section provides an overview of Finit's configuration system. For detailed information on specific topics, see the individual sections in the navigation menu.
Configuration File Syntax
The file format is line based, empty lines and comments, lines starting
with #, are ignored. A configuration directive starts with a keyword
followed by a space and the rest of the line is treated as the value.
As of Finit v4.4, configuration directives can be broken up in multiple
lines using the continuation character \, and trailing comments are
also allowed. Example:
# Escape \# chars if you want them literal in, e.g., descriptions
service name:sysklogd [S123456789] \
env:-/etc/default/sysklogd \
syslogd -F $SYSLOGD_ARGS \
-- System log daemon \# 1 # Comments allowed
The .conf files /etc/finit.conf and /etc/finit.d/* support many
directives. Some are restricted, e.g., only available at bootstrap,
runlevel S. Read on in Files & Layout for more on how
to structure your .conf files.
For details on restrictions, see Limitations.