Package: runit
Version: 1.8.0-2
Severity: minor
In testing vblade-persist in preparation for a new release in response
to #466376, i uncovered a potentially misleadeing message from
update-service:
If a service directory contains a file named "down" in it, the service
will *not* be automatically started by runsv (as specified in
runsv(8)).
That is, if you do:
mkdir -p /path/to/servicedir
cp runscript /path/to/servicedir/run
chmod a+x /path/to/servicedir/run
touch /path/to/servicedir/down
update-service --add /path/to/servicedir servicename
it will still say:
"Service servicename added, will be started within the next 5 seconds."
Fortunately, runit (correctly) doesn't actually start the service in
the next 5 seconds (or ever, unless directed to do so explicitly).
But the incorrect output message from update-service could give
someone a scare if the service really needs to stay down initially.
Thanks for maintaining runit!
--dkg
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
runit depends on no packages.
Versions of packages runit recommends:
pn fgetty <none> (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
