[shepherd] 01/01: doc: Explain where /run/user comes from.

[Ludovic Courtès]

civodul pushed a commit to branch master
in repository shepherd.

commit 02ff984f78efbc78509a8a2c22c84c3574bf4419
Author: Ludovic Courtès <address@hidden>
Date:   Wed Nov 14 21:53:34 2018 +0100

    doc: Explain where /run/user comes from.
    
    Suggested by Marius Bakke <address@hidden>
    in <https://bugs.gnu.org/33260>.
    
    * doc/shepherd.texi (Invoking shepherd): Explain where /run/user comes
    from.
---
 doc/shepherd.texi | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/shepherd.texi b/doc/shepherd.texi
index 8a5687a..3fc1cfd 100644
--- a/doc/shepherd.texi
+++ b/doc/shepherd.texi
@@ -438,7 +438,9 @@ Receive further commands on the socket special file 
@var{file}.  If this
 option is not specified, @address@hidden/run/shepherd/socket} is
 taken when running as @code{root}; when running as an unprivileged
 user, @command{shepherd} listens to @file{/run/user/@var{uid}/shepherd},
-where @var{uid} is the user's numerical ID, or to
+where @var{uid} is the user's numerical address@hidden GNU/Linux, the
address@hidden/run/user/@var{uid}} directory is typically created by elogind or 
by
+systemd, which are available in most distributions.}, or to
 @file{$XDG_RUNTIME_DIR/shepherd} when the @code{XDG_RUNTIME_DIR}
 environment variable is defined.