You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sv program can be sym-linked to /etc/init.d/ to provide an LSB init script interface. The service to be controlled then is specified by the base name of the "init script".
If sv is called with a base name other than sv: it exits 1 on timeout or trouble sending the command; if the command is status, it exits 3 if the service is down, and 4 if the status is unknown; it exits 2 on wrong usage, and 151 on error.
This isn't entirely true. If the service has a log, the exit code instead reflects the status of the log. In src/sv.c:154-176 you'll see rc updated if chdir("log") and svstatus_get() succeed, after which the if (lsb) branch to the switch will call done reflecting the log's status.
This strikes me as a bug in the code, not the man page.
The text was updated successfully, but these errors were encountered:
sv(8) says:
This isn't entirely true. If the service has a
log
, the exit code instead reflects the status of the log. In src/sv.c:154-176 you'll seerc
updated ifchdir("log")
andsvstatus_get()
succeed, after which theif (lsb)
branch to theswitch
will calldone
reflecting the log's status.This strikes me as a bug in the code, not the man page.
The text was updated successfully, but these errors were encountered: