From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 33260@debbugs.gnu.org
Subject: bug#33260: [Shepherd] ERROR: In procedure stat: No such file or directory: "/run/user/30011/shepherd
Date: Wed, 14 Nov 2018 20:37:49 +0100 [thread overview]
Message-ID: <87y39v4fhu.fsf@fastmail.com> (raw)
In-Reply-To: <87d0rg6jpk.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Marius Bakke <mbakke@fastmail.com> skribis:
>>>> What about: ‘herd status | grep logind’?
>>>
>>> No output
>>>
>>> sdb@komputilo ~$ sudo herd status |grep logind
>>>
>>>> Does /run/user exist?
>>>
>>> No
>>
>> If you add (elogind-service) to your system configuration, Shepherd
>> should work out of the box.
>
> Indeed. The Shepherd implicitly depends on elogind/systemd here.
>
> I suppose we should at least clarify this in the manual. Thoughts?
It is kind of documented under the '--socket' option of Shepherd:
https://www.gnu.org/software/shepherd/manual/shepherd.html
Perhaps a footnote to the /run/user/uid part could be added along these
lines:
"On GNU/Linux systems, this directory is typically created by a login
manager such as elogind or systemd."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-11-14 19:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 22:34 bug#33260: [Shepherd] ERROR: In procedure stat: No such file or directory: "/run/user/30011/shepherd swedebugia
2018-11-05 0:55 ` bug#33260: Invocation of per-user shepherd - design needed Danny Milosavljevic
2018-11-05 7:49 ` swedebugia
2018-11-05 8:47 ` Danny Milosavljevic
2018-11-05 7:58 ` Gábor Boskovits
2018-11-06 14:03 ` bug#33260: [Shepherd] ERROR: In procedure stat: No such file or directory: "/run/user/30011/shepherd Ludovic Courtès
2018-11-06 18:26 ` swedebugia
2018-11-07 16:36 ` Ludovic Courtès
2018-11-07 17:13 ` swedebugia
2018-11-07 18:18 ` Marius Bakke
2018-11-08 8:45 ` Ludovic Courtès
2018-11-14 19:37 ` Marius Bakke [this message]
2018-11-14 20:55 ` Ludovic Courtès
2018-11-14 21:29 ` Marius Bakke
2018-11-16 14:27 ` Danny Milosavljevic
2018-11-16 16:55 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y39v4fhu.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=33260@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.