From: ludo@gnu.org (Ludovic Courtès)
To: swedebugia <swedebugia@riseup.net>
Cc: 33260@debbugs.gnu.org
Subject: bug#33260: [Shepherd] ERROR: In procedure stat: No such file or directory: "/run/user/30011/shepherd
Date: Tue, 06 Nov 2018 15:03:41 +0100 [thread overview]
Message-ID: <877ehq2the.fsf@gnu.org> (raw)
In-Reply-To: <34806e19-072a-ce32-3a23-78e78f59b719@riseup.net> (swedebugia's message of "Sun, 4 Nov 2018 23:34:22 +0100")
Hello,
swedebugia <swedebugia@riseup.net> skribis:
> In a VM with GuixSD I did:
>
> $ shepherd
> Backtrace:
> 3 (primitive-load "/run/current-system/profile/bin/shephe…")
> In shepherd.scm:
> 164:9 2 (main . _)
> In shepherd/support.scm:
> 396:20 1 (verify-dir _ #:secure? _)
> In unknown file:
> 0 (stat "/run/user/30011/shepherd" #<undefined>)
>
> ERROR: In procedure stat:
> In procedure stat: No such file or directory: "/run/user/30011/shepherd"
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> this is a known problem in GuixSD (not in shepherd) and I don't think anyone fixed
> it yet, because it requires some design (and is kinda harder than ignoring the
> problem and letting the user choose - see below).
>
> There is only rudimentary support for distinguishing sessions from users in GuixSD
> (I guess nowadays everyone is using a computer of their own and people don't
> remember huge shared computers which you would dial into multiple times from
> different sites (not necessarily after hanging up the previous connection) -
> I work with the latter daily so I do remember).
>
> Shepherd assumes to be run per user (for non-root), not per session.
> For the vast majority of tasks-to-be-automated, that is what you want.
>
> But who starts the per-user shepherd?
I do! I run ‘shepherd’ as non-root on GuixSD, and I don’t have the
above file-not-found issue. On GuixSD, /run/user/UID is created as
expected, and I suspect it’s the same on most other GNU/Linux distros
these days.
swedebugia, what distribution are you using? On GuixSD, 30011 is a UID
that would be allocated to one of the build users, which cannot “log in”.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-11-06 14:16 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 ` Ludovic Courtès [this message]
2018-11-06 18:26 ` bug#33260: [Shepherd] ERROR: In procedure stat: No such file or directory: "/run/user/30011/shepherd 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
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=877ehq2the.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33260@debbugs.gnu.org \
--cc=swedebugia@riseup.net \
/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).