On 17/09/2015 19:33, Buck Evan wrote:
I sometimes get this result if I run s6-supervise and s6-svstat very close together:
Yes. It happens when the service has just been launched and has not even tried to come up yet. Known issue, purely cosmetic; I'll try and fix it in the next release. -- Laurent
