GNU bug report logs -
#33270
[SHEPHERD] Wrong error message when missing priviledge
Previous Next
Full log
View this message in rfc822 format
Hello Ricardo,
Ricardo Wurmus <rekado <at> elephly.net> ezt írta (időpont: 2018. nov. 5., H, 20:50):
>
>
> swedebugia <swedebugia <at> riseup.net> writes:
>
> > sdb <at> 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
This bug report was last modified 6 years and 220 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.