X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fdaemon.xml;h=a23a04794b2a5e1cee35fe46f73cae8682c0704f;hb=bf32f99f65ec42539af65736b057c9e09d3987b9;hp=fd29ba722d7d131387b5210dcb05df891d23ef51;hpb=41a55c46ab8fb4ef6727434227071321fc762cce;p=elogind.git
diff --git a/man/daemon.xml b/man/daemon.xml
index fd29ba722..a23a04794 100644
--- a/man/daemon.xml
+++ b/man/daemon.xml
@@ -74,8 +74,8 @@
Close all open file
- descriptors except stdin, stdout,
- stderr (i.e. the first three file
+ descriptors except standard input, output,
+ and error (i.e. the first three file
descriptors 0, 1, 2). This ensures
that no accidentally passed file
descriptor stays around in the daemon
@@ -158,9 +158,7 @@
it is verified at the same time that
the PID previously stored in the PID
file no longer exists or belongs to a
- foreign process. Commonly, some kind of
- file locking is employed to implement
- this logic.
+ foreign process.
In the daemon process,
drop privileges, if possible and
@@ -252,7 +250,7 @@
detect service errors and problems. It
is recommended to follow the exit code
scheme as defined in the LSB
+ url="http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html">LSB
recommendations for SysV init
scripts.
@@ -323,29 +321,21 @@
interface.
Instead of using the
- syslog() call to log directly to the
- system syslog service, a new-style daemon may
- choose to simply log to standard error via
- fprintf(), which is then forwarded to
- syslog by the init system. If log
- priorities are necessary, these can be
- encoded by prefixing individual log
- lines with strings like "<4>"
- (for log priority 4 "WARNING" in the
- syslog priority scheme), following a
- similar style as the Linux kernel's
- printk() priority system. In fact,
- using this style of logging also
- enables the init system to optionally
- direct all application logging to the
- kernel log buffer (kmsg), as
- accessible via
- dmesg1. This
- kind of logging may be enabled by
- setting
- StandardError=syslog
- in the service unit file. For details,
- see
+ syslog() call to
+ log directly to the system syslog
+ service, a new-style daemon may choose
+ to simply log to standard error via
+ fprintf(), which
+ is then forwarded to syslog by the
+ init system. If log priorities are
+ necessary, these can be encoded by
+ prefixing individual log lines with
+ strings like "<4>" (for log
+ priority 4 "WARNING" in the syslog
+ priority scheme), following a similar
+ style as the Linux kernel's
+ printk() priority
+ system. For details, see
sd-daemon3
and
systemd.exec5.
@@ -354,7 +344,7 @@
These recommendations are similar but
not identical to the Apple
+ url="https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html">Apple
MacOS X Daemon Requirements.
@@ -395,7 +385,7 @@
exclusively on boot (and manually by the
administrator) via SysV init scripts, as
detailed in the LSB
+ url="http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html">LSB
Linux Standard Base Core
Specification. This method of
activation is supported ubiquitously on Linux
@@ -758,7 +748,7 @@
boot.
Packages using
- autoconf1
+ autoconf1
are recommended to use a configure script
excerpt like the following to determine the
unit installation path during source
@@ -793,7 +783,7 @@ AM_CONDITIONAL([HAVE_SYSTEMD], [test "x$with_systemdsystemunitdir" != "xno"])
Makefile.am
file in
- automake1-based
+ automake1-based
projects:
DISTCHECK_CONFIGURE_FLAGS = \
@@ -808,7 +798,7 @@ systemdsystemunit_DATA = \
endif
In the
- rpm8
+ rpm8
.spec file, use snippets
like the following to enable/disable the
service during
@@ -942,6 +932,14 @@ fi
+
+ Placing Daemon Data
+
+ It is recommended to follow the general
+ guidelines for placing package files, as discussed in
+ file-hierarchy7.
+
+
See Also
@@ -950,7 +948,8 @@ fi
sd_listen_fds3,
sd_notify3,
daemon3,
- systemd.service5
+ systemd.service5,
+ file-hierarchy7