[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [SHEPHERD]: Could not start manually as user
From: |
Efraim Flashner |
Subject: |
Re: [SHEPHERD]: Could not start manually as user |
Date: |
Mon, 18 May 2020 17:41:10 +0300 |
On Mon, May 18, 2020 at 09:31:18AM -0400, Raghav Gururajan wrote:
> Hello Guix!
>
> I need help with the following:
>
> [1]
>
> When I manually start shepherd as user, the get the error,
>
> *** START ***
> rg@secondary ~$ shepherd
> Backtrace:
> 3 (primitive-load "/run/current-system/profile/bin/shephe…")
> In shepherd.scm:
> 174:9 2 (main . _)
> In shepherd/support.scm:
> 388:20 1 (verify-dir _ #:secure? _)
> In unknown file:
> 0 (stat "/run/user/1000/shepherd" #<undefined>)
>
> ERROR: In procedure stat:
> In procedure stat: No such file or directory: "/run/user/1000/shepherd"
> *** END ***
>
> What is the correct way to rectify this?
It looks like '/run/user/1000/shepherd' doesn't exist. I suppose the
error message could be better, shepherd can't create its socket in that
directory if it can't write to it.
One option is to start shepherd with 'shepherd
--socket=~/.config/shepherd/shepherd.sock' which will use a directory
which should exist already.
> P.S. efraim and lfam, starting a thread to discuss. :-)
>
> [2]
>
> Is there a way to automatically start shepherd as user, when I log-in?
> Script or Cron?
I start mine by hand. Unfortunately mcron doesn't have support for the
'@' notation, so '@reboot' doesn't work.
>
> Thank you!
>
> Regards,
> RG.
>
--
Efraim Flashner <address@hidden> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature