[Bug 814797] New: Daemons with LSB init scripts only don't work
https://bugzilla.novell.com/show_bug.cgi?id=814797 https://bugzilla.novell.com/show_bug.cgi?id=814797#c0 Summary: Daemons with LSB init scripts only don't work Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: kukuk@suse.com QAContact: qa-bugs@suse.de CC: aj@suse.com, mge@suse.com, fcrozat@suse.com Found By: --- Blocker: Yes Install a package with a standard SUSE or LSB initscript, which does not have yet a systemd service file. If you start the service, the call will be redirected to systemctl start, which will of course fail, since no service file for this daemon exits. The redirect should never happen for standard LSB initscripts, especially not if there is no service file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=814797
https://bugzilla.novell.com/show_bug.cgi?id=814797#c1
--- Comment #1 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=814797
https://bugzilla.novell.com/show_bug.cgi?id=814797#c2
--- Comment #2 from Thorsten Kukuk
https://bugzilla.novell.com/show_bug.cgi?id=814797
https://bugzilla.novell.com/show_bug.cgi?id=814797#c
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=814797
https://bugzilla.novell.com/show_bug.cgi?id=814797#c3
--- Comment #3 from Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=814797
https://bugzilla.novell.com/show_bug.cgi?id=814797#c4
--- Comment #4 from Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=814797
https://bugzilla.novell.com/show_bug.cgi?id=814797#c6
--- Comment #6 from Frederic Crozat
Would we need to monitor /etc/init.d ourselves for new files - or reread it in case of errors?
Monitoring /etc/init.d can't be done (same for systemd own directories) because systemd has no way to know when an update is in progres and when it should reload (you don't want to reload stuff from disk in the middle of an upgrade) We could add some "systemctl daemon-reload" magic in /etc/rc.status magic if the initscript hasn't been loaded. Maybe systemd could create a timestamp on /run/systemd when it reloads its config and /etc/rc.status to use it to autoreload its config if /etc/init.d modification time is older than that.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=814797
https://bugzilla.novell.com/show_bug.cgi?id=814797#c
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=814797
https://bugzilla.novell.com/show_bug.cgi?id=814797#c
Matthias Eckermann
https://bugzilla.novell.com/show_bug.cgi?id=814797
https://bugzilla.novell.com/show_bug.cgi?id=814797#c8
Dr. Werner Fink
participants (1)
-
bugzilla_noreply@novell.com