[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 <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #1 from Dr. Werner Fink <werner@suse.com> 2011-11-08 16:31:20 UTC --- Even if systemd is not running but installed the service should be enabled as otherwise switching back to systemd would miss a service. Frederic? Why does systemctl return an error ... this should work e.g. for a missed service enabled during a rescure boot shell session? -- 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#c2 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #2 from Frederic Crozat <fcrozat@suse.com> 2011-11-08 16:48:31 UTC --- systemctl doesn't rely on systemd running for enable and disable command, so those commands are correctly handled even when running under sysvinit. After checking systemctl code, returned error is coming from : if (!arg_no_reload) r = daemon_reload(bus, args); because by default systemctl is notifying systemd to reload its configuration. Maybe insserv could pass --no-reload to systemctl if systemd isn't running -- 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#c3 --- Comment #3 from Dr. Werner Fink <werner@suse.com> 2011-11-09 11:57:51 UTC --- Created an attachment (id=461162) --> (http://bugzilla.novell.com/attachment.cgi?id=461162) Do you have meant soemthing like 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=728947 https://bugzilla.novell.com/show_bug.cgi?id=728947#c4 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #4 from Dr. Werner Fink <werner@suse.com> 2011-11-09 11:59:55 UTC --- This one uses --no-reload for the chroot case as well as for the case /sys/fs/cgroup/systemd is not mounted as cgroupfs -- 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#c5 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|fcrozat@suse.com |lnussel@suse.com --- Comment #5 from Frederic Crozat <fcrozat@suse.com> 2011-11-09 12:15:47 UTC --- sounds good (but not tested). ludwig, could you test in your environment ? -- 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#c7 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|lnussel@suse.com | --- Comment #7 from Ludwig Nussel <lnussel@suse.com> 2011-11-09 16:35:15 CET --- still complains about an error and indeed systemctl returns status 1, independent of whether --no-reload is specified or not. -- 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#c8 --- Comment #8 from Ludwig Nussel <lnussel@suse.com> 2011-11-09 16:37:40 CET --- unit_file_enable(): 1414 /* This will return the number of symlink rules that were 1415 supposed to be created, not the ones actually created. This is 1416 useful to determine whether the passed files hat any 1417 installation data at all. */ 1418 r = install_context_apply(&c, &paths, config_path, root_dir, force, changes, n_changes); So I suppose it returns a number here and uses that as exit code. -- 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#c9 Ruediger Meier <sweet_f_a@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sweet_f_a@gmx.de --- Comment #9 from Ruediger Meier <sweet_f_a@gmx.de> 2011-11-12 13:49:42 UTC --- I wonder why insserv has been patched for systemd support at all? It's made for sysvinit. When using sysvinit rather than systemd I don't want to get botherd by any systemd related things. Moreover the systemd integration patch invalidates the man page. So please remove insserv's systemd patches completely. To be user friendly I could only imagine a wrapper script which warns you like that "Warning, insserv doesn't work for your installed systemd" -- 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#c10 --- Comment #10 from Dr. Werner Fink <werner@suse.com> 2011-11-18 14:25:10 UTC --- (In reply to comment #9) 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. This enforces tht both systemd and SysVinit will be hold in sync and the user is able to switch the init daemon. -- 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#c11 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #11 from Dr. Werner Fink <werner@suse.com> 2011-11-18 14:32:44 UTC --- (In reply to comment #8) I'd like to ask what exactly does thos return values mean? -- 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#c12 --- Comment #12 from Bernhard Wiedemann <bwiedemann@suse.com> 2011-11-18 16:00:09 CET --- This is an autogenerated message for OBS integration: This bug (728947) was mentioned in https://build.opensuse.org/request/show/92409 Factory / insserv -- 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#c13 --- Comment #13 from Ruediger Meier <sweet_f_a@gmx.de> 2011-11-18 15:15:27 UTC --- (In reply to comment #10)
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 <fcrozat@suse.com> 2011-11-18 15:15:49 UTC --- from the manpage, error code from systemctl is 0 : no error, non-zero, an error occurred, but it is not specified which one (and from a quick look at the code, it is usually sending EXIT_FAILURE (ie 1) when something wrong was detected.. -- 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#c15 --- Comment #15 from Dr. Werner Fink <werner@suse.com> 2011-11-18 15:37:18 UTC --- (In reply to comment #13) 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. -- 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#c16 --- Comment #16 from Ruediger Meier <sweet_f_a@gmx.de> 2011-11-18 15:48:55 UTC --- (In reply to comment #15)
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 <werner@suse.com> 2011-11-18 16:07:45 UTC --- (In reply to comment #16) and insserv does the rm/ln job for the admin -- 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#c18 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |werner@suse.com InfoProvider|fcrozat@suse.com | AssignedTo|werner@suse.com |fcrozat@suse.com --- Comment #18 from Dr. Werner Fink <werner@suse.com> 2011-11-29 18:28:54 UTC --- Please make systemd work even with the extensions and features provided by the LSB boot scheme of the old SysVinit of openSUSE. -- 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#c19 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #19 from Frederic Crozat <fcrozat@suse.com> 2013-03-11 16:09:49 UTC --- (In reply to comment #18)
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