From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 33270@debbugs.gnu.org
Subject: bug#33270: [SHEPHERD] Wrong error message when missing priviledge
Date: Mon, 5 Nov 2018 22:57:15 +0100 [thread overview]
Message-ID: <CAE4v=phMy1QLf+T5VyP+9h8wN5xG+xrXHVqcAWQTUgiP9Rhi2g@mail.gmail.com> (raw)
In-Reply-To: <87muqnwbj0.fsf@elephly.net>
Hello Ricardo,
Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2018. nov. 5., H, 20:50):
>
>
> swedebugia <swedebugia@riseup.net> writes:
>
> > sdb@komputilo ~$ herd status
> > error: connect: /run/user/30011/shepherd/socket: No such file or directory
>
Actually this seems to be a message that can be translated to
'shepherd user instance is not running' am I correct?
I guess that way it is explicit that the command given would like to
talk to a shepherd user instance. Am I missing something here?
> It is possible to run shepherd as a user service manager. This means
> that we can’t generally assume that the user meant to communicate with
> the init instance.
>
> The error could be that either the user’s instance is not running or
> that the user meant to communicate with the init system. It is not
> obvious to me how to distinguish these two errors.
>
> --
> Ricardo
>
>
>
>
Best regards,
g_bor
next prev parent reply other threads:[~2018-11-05 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 9:55 bug#33270: [SHEPHERD] Wrong error message when missing priviledge swedebugia
2018-11-05 19:48 ` Ricardo Wurmus
2018-11-05 21:57 ` Gábor Boskovits [this message]
2018-11-05 22:49 ` Danny Milosavljevic
2018-11-06 7:55 ` Gábor Boskovits
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='CAE4v=phMy1QLf+T5VyP+9h8wN5xG+xrXHVqcAWQTUgiP9Rhi2g@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=33270@debbugs.gnu.org \
--cc=rekado@elephly.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).