X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fdaemon.xml;h=258694080e22600b10089daf2caabcadccc6ad6a;hb=74d005783e355acc784d123024e33bbb66ef9ef1;hp=83143dc4b263519c6dcd64a8d7c39a54c149a9c8;hpb=cb07866b1b7c11e687a322d70dd9f9d73bbbe488;p=elogind.git
diff --git a/man/daemon.xml b/man/daemon.xml
index 83143dc4b..258694080 100644
--- a/man/daemon.xml
+++ b/man/daemon.xml
@@ -44,7 +44,7 @@
daemon
- Writing and Packaging System Daemons
+ Writing and packaging system daemons
@@ -122,7 +122,7 @@
first child, so that only the second
child (the actual daemon process)
stays around. This ensures that the
- daemon process is reparented to
+ daemon process is re-parented to
init/PID 1, as all daemons should
be.
@@ -181,11 +181,11 @@
exit() in the
original process. The process that
invoked the daemon must be able to
- rely that this
+ rely on that this
exit() happens
after initialization is complete and
all external communication channels
- established and
+ are established and
accessible.
@@ -196,7 +196,7 @@
compatibility with SysV systems should
implement the scheme pointed out
above. However, it is recommended to make this
- behaviour optional and configurable via a
+ behavior optional and configurable via a
command line argument, to ease debugging as
well as to simplify integration into systems
using systemd.
@@ -271,7 +271,7 @@
for details.
As much as possible,
- rely on the init systemd's
+ rely on the init system's
functionality to limit the access of
the daemon to files, services and
other resources. i.e. in the case of
@@ -462,7 +462,7 @@
New-style daemons which support socket
activation must be able to receive their
- sockets from the init system, instead of of
+ sockets from the init system, instead of
creating and binding them themselves. For
details about the programming interfaces for
this scheme provided by systemd see
@@ -547,7 +547,7 @@
systemd, kernel devices appearing in the
sysfs/udev device tree can be exposed as units
if they are tagged with the string
- "systemd". Like any other
+ systemd. Like any other
kind of unit they may then pull in other units
when activated (i.e. Plugged in) and thus
implement device-based activation. Systemd
@@ -740,7 +740,7 @@
directory returned by pkg-config
systemd
--variable=systemdsystemunitdir (for
- system services), resp. pkg-config
+ system services) or pkg-config
systemd
--variable=systemduserunitdir
(for user services). This will make the
@@ -894,7 +894,7 @@ fi
If the daemon offers
interfaces to other software running on the
- local system via local AF_UNIX sockets,
+ local system via local AF_UNIX sockets,
consider implementing socket-based activation
(see above). Usually a minimal patch is
sufficient to implement this: Extend the
@@ -905,8 +905,8 @@ fi
sd_listen_fds() returns a
positive value), skip the socket creation step
and use the passed sockets. Secondly, ensure
- that the file-system socket nodes for local
- AF_UNIX sockets used in the socket-based
+ that the file system socket nodes for local
+ AF_UNIX sockets used in the socket-based
activation are not removed when the daemon
shuts down, if sockets have been
passed. Third, if the daemon normally closes