http://bugzilla.opensuse.org/show_bug.cgi?id=901796 Rakshika Gupta changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|systemctl status returns |systemctl status returns |zero exit code even if |with zero exit code even if |service is not running or |service is not running or |in failed state |in failed state -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901796 Rakshika Gupta changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #3 from Rakshika Gupta --- As you have specified above, "systemctl is-active <service>" returns non-zero exit code if service is not running or in failed state. So, non-zero exit code is expected from command "systemctl status <service>" also if service is not running or in failed state. We have other system installed with RHEL7 on which "systemctl status <service>" returns a non-zero exit code if service is not running or in failed state. eg: On RHEL7 system, we see this behavior; # systemctl status smb smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled) Active: failed (Result: core-dump) since Tue 2014-10-21 11:51:56 EDT; 16s ago Process: 31946 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=dumped, signal=ABRT) Main PID: 31946 (code=dumped, signal=ABRT) Status: "smbd: ready to serve connections..." # echo $? 3 Most of our applications rely on correct exit code of "systemctl status <service>". Will you fixing this bug in SLES 12 GA release ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901796 --- Comment #4 from Bernhard Wiedemann --- btw: on openSUSE-12.3 and SLE12 with systemd I can still do rcapache2 stop rcapache2 status ; echo $? 3 but when trying the same with rclighttpd it always gives a result of 0 The difference being that there is a /usr/lib/systemd/system/apache2.service but no lighttpd.service This points to the sysvinit-compat layer being broken. SYSTEMD_NO_WRAP=1 rclighttpd status ; echo $? Checking for service lighttpd 7 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901796 Lars Müller changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |samba-maintainers@SuSE.de Assignee|lmuelle@suse.com |systemd-maintainers@suse.de Flags| |needinfo?(rakshika.gupta@hp | |.com) --- Comment #5 from Lars Müller --- Is this the issue you see? e10:~ # systemctl start cups.service e10:~ # systemctl status cups.service cups.service - CUPS Printing Service Loaded: loaded (/usr/lib/systemd/system/cups.service; disabled) Active: active (running) since Di 2014-10-21 17:26:11 CEST; 4s ago Main PID: 6315 (cupsd) CGroup: /system.slice/cups.service └─6315 /usr/sbin/cupsd -f e10:~ # kill -SEGV 6315 e10:~ # systemctl status cups.service cups.service - CUPS Printing Service Loaded: loaded (/usr/lib/systemd/system/cups.service; disabled) Active: failed (Result: signal) since Di 2014-10-21 17:26:32 CEST; 2s ago Process: 6315 ExecStart=/usr/sbin/cupsd -f (code=killed, signal=SEGV) Main PID: 6315 (code=killed, signal=SEGV) e10:~ # echo $? 0 And instead of 0 as return value you like to get 3 returned here. Right? I've tried the same with the smb and atd services too and they behave identical. Therefore I'm passing the issue back to the systemd maintainers but request information from the reporter. Also the bug product should be reevaluated. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901796 --- Comment #10 from Johannes Meixner --- Yes. I only liked to point out that "rcfoo status" is backward compatible while "systemctl status foo" results the new upstream behaviour. -- You are receiving this mail because: You are on the CC list for the bug.