https://bugzilla.novell.com/show_bug.cgi?id=384254 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=384254#c46 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@novell.com AssignedTo|werner@novell.com |jkupec@novell.com Severity|Critical |Blocker Status|NEEDINFO |NEW Info Provider|werner@novell.com | --- Comment #46 from Dr. Werner Fink <werner@novell.com> 2008-05-14 09:09:43 MST --- In other words insserv should not throw out any error if an error happens for a single rpm? If a user turns off a single script (e.g. boot.setclock) the the single installation of nscd should throw an error is insservs runs on an error. And yes your system is currently broken and can only be repaired by hand. For an update of a system with changing dependcies between boot/init scripts such errors should be ignored due to the fact that such an error is temporary upto the point where all packages are uptodate. Please note that insserv(8) does not know about simple rpm call nor YaST update nor zypper nor zyppers dup option. It has an simple option -f for ignoring if a required service is missed. Therefore this bug does not belong to me. If zypper has a way to inform all sub processes whats going on (update of a system or single installation of an rpm) then please inform me because then I've to adapt this within 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.