Re: wrong exit code for sv status in lsb mode

2019-01-08 Thread David Mountney via supervision
The error was introduced in commit 5fe1bc773c2d979093fe4b1f3ecbbed5e6acdaf0 "sv.c: properly format status command's output on failure cases." Where the log status is being saved to the same variable as the service status. The quick fix would be to not record the log status for now: $ git diff

Re: Can s6 be enough?: was s6-ps

2019-01-08 Thread Laurent Bercot
When Debian acquires a properly working s6-rc package, the answer to my question degenerates to "why not?" But for now, for the Debian person who only installs via package, s6-rc is out of the question, so my question was, isn't s6 itself good enough? Then maybe you should ask Debian instead,

Re: wrong exit code for sv status in lsb mode

2019-01-08 Thread Gerrit Pape
Hi, donations for my free software increased recently, not sure why, but thanks. runit upstream sources with history still are available through $ git clone http://smarden.org/git/runit.git Below is the diff for sv.c from 2.1.1 to 2.1.2. Possibly anyone can spot the error and create a patch