Debian init script: status command exit code is always 0

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • Component/s: core
    • Environment:
      Debian Lenny (5.0.9), Jenkins 1.434

      Under debian Lenny, the /etc/init.d/jenkins status script always exit with return code 0, even it the service is not running. According to LSB standard, the return code should be the following:

      • 0 program is running or service is OK;
      • 1 program is dead and /var/run pid file exists;
      • 3 program is not running.

      Found on https://fedoraproject.org/wiki/FCNewInit/Initscripts#Init_Script_Actions as official LSB website is currently down.

      This fixed status code is quite annoying if we rely on the init script for monitoring purpose.

            Assignee:
            Unassigned
            Reporter:
            Reynald Borer
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: