[Bug 728947] New: insserv tries to use systemd even when booted with sysvinit
https://bugzilla.novell.com/show_bug.cgi?id=728947 https://bugzilla.novell.com/show_bug.cgi?id=728947#c0 Summary: insserv tries to use systemd even when booted with sysvinit Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: werner@suse.com ReportedBy: lnussel@suse.com QAContact: qa@suse.de CC: fcrozat@suse.com Found By: --- Blocker: --- insserv probably should not try to redir to systemd if systemd isn't actually used as it throws an error otherwise: # insserv avahi-daemon insserv: Note: sysvinit service avahi-daemon is shadowed by systemd avahi-daemon.service, Forwarding request to '/bin/systemctl enable avahi-daemon.service'. insserv: Forward service request to systemctl returned error status : 768 -- 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=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c1
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c2
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c3
--- Comment #3 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c4
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c5
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c7
Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c8
--- Comment #8 from Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c9
Ruediger Meier
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c10
--- Comment #10 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c11
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c12
--- Comment #12 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c13
--- Comment #13 from Ruediger Meier
This will not happen due the simple reason that *most* people expect that insserv will enable a service even if provided by a systemd service unit.
On the other hand the only reason why some users stick with sysvinit at all is that they want the old stable non-patched thing. It's a pity that deploying systemd also affected sysvinit.
This enforces tht both systemd and SysVinit will be hold in sync and the user is able to switch the init daemon.
Couldn't it be synced somehow when the user is actually switching? If you do a fresh systemd install then it starts from scratch too. Morever if user is using whatever other tool to set init links then they are not in sync anyway. What about conflicting systemd-sysvinit and sysvinit-init packages and also update-alternative insserv? BTW getting rid of the "systemd/sysvinit sync" could also make it possible to remove a lot of the last systemd deps. -- 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=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c14
--- Comment #14 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c15
--- Comment #15 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c16
--- Comment #16 from Ruediger Meier
Please hold in mind tat systemd supports LSB boot scripts and therefore insserv should be there to enable those services ... this one is one of the major features of systemd to be able to support every LSB boot script.
My understanding is that this support needs to be implemented within systemd and not sysvinit/insserv. When using rm/ln to configure init links systemd should respect this too if it wants to be compatible. -- 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=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c17
--- Comment #17 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c18
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c19
Frederic Crozat
Please make systemd work even with the extensions and features provided by the LSB boot scheme of the old SysVinit of openSUSE.
this is now the case in recent openSUSE. Closing as fixed -- 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.
participants (1)
-
bugzilla_noreply@novell.com