From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: 33260@debbugs.gnu.org
Subject: bug#33260: [Shepherd] ERROR: In procedure stat: No such file or directory: "/run/user/30011/shepherd
Date: Thu, 08 Nov 2018 09:45:43 +0100 [thread overview]
Message-ID: <87d0rg6jpk.fsf@gnu.org> (raw)
In-Reply-To: <87muqkzr8b.fsf@fastmail.com> (Marius Bakke's message of "Wed, 07 Nov 2018 19:18:12 +0100")
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?
> Alternatively, I do this on a minimal system:
>
> # Shepherd requires that this variable is set unless logind is present.
> export XDG_RUNTIME_DIR="${HOME}/.local/run"
>
> # ...and does not clean up its own socket after use.
> rm -f "$XDG_RUNTIME_DIR/shepherd/socket"
>
> # Now we can start it.
> shepherd &
Neat.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-11-08 8:51 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 [this message]
2018-11-14 19:37 ` Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0rg6jpk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33260@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).