On Fri, Feb 01, 2019 at 04:18:50AM +, Kelly Dean wrote:
> Thanks for the fix. Longrun works now, though oneshot still fails, this time
> with a different message:
> s6-sudoc: fatal: connect to the s6-sudod server - check that you have
> appropriate permissions.
>
> I guess that's related to
On Fri, Feb 01, 2019 at 04:18:50AM +, Kelly Dean wrote:
>
> Thanks for the fix. Longrun works now, though oneshot still fails, this time
> with a different message:
> s6-sudoc: fatal: connect to the s6-sudod server - check that you have
> appropriate permissions.
>
> I guess that's related
Thanks for the fix. Longrun works now, though oneshot still fails, this time
with a different message:
s6-sudoc: fatal: connect to the s6-sudod server - check that you have
appropriate permissions.
I guess that's related to my running all this (including svscan) as non-root.
s6rc-oneshot-runn
s6-svc -wu -u serv/foo/ will start it, but never exits. Likewise, s6-svc -wd -d
serv/foo/ will stop it, but never exits.
Now that is probably due to your setup, because yours is the only
report I have of it not working.
Update: just tonight I received another report of the exact same
symptom
Laurent Bercot:
s6-svscan is pretty mild in that aspect.
In fairness, the original Bernstein program was somewhat more forgiving:
> /package/admin/djbwares % command/svscan --help
> svscan: fatal: unable to chdir to --help: file does not exist
> /package/admin/djbwares %
People used this prog
mkdir test
s6-svscan --help
Well, that was surprising and unpleasant. It ignores unknown arguments,
blithely starts a supervision tree in the current dir (my home dir), and spams
me with a bunch of supervise errors. Ok, kill it.
Next test:
s6-svscan test
Do you always run programs you don't k
Kelly Dean writes:
> In serv/foo/run I have:
> #/bin/bash
> echo starting; sleep 2; echo dying
Just a typo in my message. Actual file does have #!/bin/bash
mkdir test
s6-svscan --help
Well, that was surprising and unpleasant. It ignores unknown arguments,
blithely starts a supervision tree in the current dir (my home dir), and spams
me with a bunch of supervise errors. Ok, kill it.
Next test:
s6-svscan test
It gives errors about supervise being un
