Your message dated Sun, 31 Jul 2016 13:31:10 +0300 with message-id <[email protected]> and subject line State of custom sv commands has caused the Debian Bug report #375433, regarding Please support custom commands in sv and/or runsv to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 375433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375433 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: runit Version: 1.5.1-1 Severity: wishlist Hi, it'd be nice (for example during upgrades) if "/etc/init.d/gdm reload" could be made to work even if gdm is run supervised and /etc/init.d/gdm is a symlink to /usr/bin/sv. Arbitrary commands could be supported, provided the administrator supplied the appropriate action script. If these scripts could affect the output of sv(8), that would be wonderful, but probably hard to do in a robust way. Quite a few initscripts support numerous commands in addition to the standard start/stop/force-*, and replacing them with runit's sv would be a lot less painful if these could be supported transparently. I realize there is a difficulty with the one-character control fifo protocol, but I think there are several ways around that (for example, a new fifo could be used for the custom commands; that way, backward compatibility with daemontools could be retained). Regards, Andras -- Andras Korn <korn at chardonnay.math.bme.hu> <http://chardonnay.math.bme.hu/~korn/> QOTD: I must follow them; I am their leader.
--- End Message ---
--- Begin Message ---Current runit-2.1.2 supports sysv-compatible commands: From runsv(8): For each control character c sent to the control pipe, runsv first checks if service/control/c exists and is executable. If so, it starts service/control/c and waits for it to terminate, before interpreting the command. If the program exits with return code 0, runsv refrains from sending the service the corresponding signal. The command o is always considered as command u. On command d first service/control/t is checked, and then service/control/d. On command x first ser‐ vice/control/t is checked, and then service/control/x. The control of the optional log service cannot be customized. From sv(8): Commands compatible to LSB init script actions status Same as status. start Same as up, but wait up to 7 seconds for the command to take effect. Then report the status or timeout. If the script ./check exists in the service directory, sv runs this script to check whether the service is up and available; it's considered to be available if ./check exits with 0. stop Same as down, but wait up to 7 seconds for the service to become down. Then report the status or timeout. reload Same as hup, and additionally report the status afterwards. restart Send the commands term, cont, and up to the service, and wait up to 7 seconds for the service to restart. Then report the status or timeout. If the script ./check exists in the service direc‐ tory, sv runs this script to check whether the service is up and available again; it's considered to be available if ./check exits with 0. shutdown Same as exit, but wait up to 7 seconds for the runsv(8) process to terminate. Then report the status or timeout. force-stop Same as down, but wait up to 7 seconds for the service to become down. Then report the status, and on timeout send the service force-reload Send the service the term and cont commands, and wait up to 7 seconds for the service to restart. Then report the status, and on timeout send the service the kill command. force-restart Send the service the term, cont and up commands, and wait up to 7 seconds for the service to restart. Then report the status, and on timeout send the service the kill command. If the script ./check exists in the service directory, sv runs this script to check whether the service is up and available again; it's con‐ sidered to be available if ./check exits with 0. force-shutdown Same as exit, but wait up to 7 seconds for the runsv(8) process to terminate. Then report the status, and on timeout send the service the kill command. try-restart if the service is running, send it the term and cont commands, and wait up to 7 seconds for the service to restart. Then report the status or timeout. -- Accept: text/plain, text/x-diff Accept-Language: eo,en,ru X-Web-Site: sinsekvu.github.io
pgpZydPKQsmb0.pgp
Description: PGP signature
--- End Message ---
