+++ This bug was initially created as a clone of Bug #749987 +++ > In that case it would make sense to exit the initscript with a different exit > code than 0. One of these LSB defined codes would do: > 6: program is not configured > 7: program is not running Not sure if this helped or not. I did this: diff --git a/iscsid.init b/iscsid.init index c208ccc..7dff612 100755 --- a/iscsid.init +++ b/iscsid.init @@ -82,7 +82,8 @@ start() { return $? fi - return 0 + # There are no targets configured to run. + exit 6 } stop() { And now I get (it used to report success): service iscsid start Starting iscsid (via systemctl): Job failed. See system logs and 'systemctl status' for details. [FAILED] but systemd still reports: Feb 1 18:09:36 madmax systemd[1]: PID file /var/run/iscsid.pid not readable (yet?) after start. Feb 1 18:09:36 madmax systemd[1]: Unit iscsid.service entered failed state. This error message about the PID is slightly different. I think the systemd message is incorrrect here though. It should not be reporting the PID message i this case because we already know that the service did not start correctly.
/etc/rc.d/init.d/iscsid is an LSB initscript and systemd considers LSB exit code 6/NOTCONFIGURED as clean, thus it will execute code which should be executed only for forking services which really succeeded to start and has written a PID file. This is not the case for initscript returning exit code 6/NOTCONFIGURED, hence logged error message about not readable PID file. Obvious solution is to stop considering exit code 6 as clean, however this might have some consequences I am not aware of. Since this is still an issue, moving this bug report against Rawhide.
Arguably the iscsid should be migrated ( and fixed in the process ) but there is no one working on it afaik ( see bug 714688 )
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.