Univention Bugzilla – Bug 38232
Policy violation: /etc/init.d/univention-s4-connector not idempotent
Last modified: 2020-07-04 08:35:05 CEST
Created attachment 6818 [details] s4c: Fix init behaviour Stopping the S4C multiples times fails: > # /etc/init.d/univention-s4-connector stop > [info] Stopping univention-s4-connector daemon. > done. > # /etc/init.d/univention-s4-connector stop > [info] Stopping univention-s4-connector daemon. > start-stop-daemon: warning: failed to kill 6505: No such process > failed. This is in violation of <https://www.debian.org/doc/debian-policy/ch-opersys.html#s-writing-init>: > The init.d scripts must ensure that they will behave sensibly (i.e., returning success [...] with stop when it isn't [running ...] +++ This bug was initially created as a clone of Bug #35557 +++
This is a Jenkins regression: <http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/UCS-4.0-1/job/Autotest%20MultiEnv/SambaVersion=s4,Systemrolle=backup/64/testReport/junit/01_base/99check_log_files/test/>
2015-04-12 S4,Backup <http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/UCS-4.0-1/job/Autotest%20MultiEnv/SambaVersion=s4,Systemrolle=backup/67/testReport/junit/01_base/99check_log_files/test/>
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
This is fixed because systemd is used, which handles this case correctly.