From: Danny Milosavljevic <dannym@scratchpost.org>
To: swedebugia <swedebugia@riseup.net>
Cc: 33260@debbugs.gnu.org
Subject: bug#33260: Invocation of per-user shepherd - design needed
Date: Mon, 5 Nov 2018 09:47:56 +0100 [thread overview]
Message-ID: <20181105094726.3af2b9df@scratchpost.org> (raw)
In-Reply-To: <eb7113ef-09b3-5127-bda4-2692ab056f3e@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
Hi,
On Mon, 5 Nov 2018 08:49:00 +0100
swedebugia <swedebugia@riseup.net> wrote:
> # sudo herd status
>
> gave me what I wanted
>
> Maybe an error to the non-root user such as: "Shepherd is designed to
> run as root only" would suffice.
shepherd is not designed to run as root only. That's exactly why it's trying
to connect to the per-user instance: If there's one, it will work fine. If
not, you get this error message (we should improve the error message to not
include a stack trace - and also maybe add a hint to it about what to do).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-05 8:52 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 [this message]
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
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=20181105094726.3af2b9df@scratchpost.org \
--to=dannym@scratchpost.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).