Package: runit Version: 2.1.1-6.2 Severity: minor
This is pretty unlikely to happen in normal usage, but I ran across it doing some testing of "sv status" behaviors; if sv is given multiple service directories to operate on, and some of them don't have an active runsv process "sv status" may report misleading information: Given two service directories: # ls testapp1 run supervise # ls testapp2 log run supervise where testapp1 is running, and testapp2 isn't: # sv status ./testapp1 run: ./testapp1: (pid 3682) 408178s # sv status ./testapp2 fail: ./testapp2: runsv not running # sv status ./testapp1 ./testapp2 run: ./testapp1: (pid 3682) 408184s fail: ./testapp2: runsv not running run: ./testapp2: (pid 3682) 408184sfail: ./testapp2: runsv not running That third line is the issue, afaics it shouldn't exist at all. Scanned in the other order the result is as expected: # sv status ./testapp2 ./testapp1 fail: ./testapp2: runsv not running run: ./testapp1: (pid 3682) 409683s Looks like something isn't being re-initialized correctly in the error path. Again, pretty unlikely to occur in normal usage where one is always using sv status against actively supervised services, but it could possibly occur in the time between runsv being told to exit and runsvdir restarting runsv. -- Jamie Heilman http://audible.transient.net/~jamie/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
