[Bug 736667] New: libc was updated and no reboot was suggested.
https://bugzilla.novell.com/show_bug.cgi?id=736667 https://bugzilla.novell.com/show_bug.cgi?id=736667#c0 Summary: libc was updated and no reboot was suggested. Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: VMWare OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: carlos.e.r@opensuse.org QAContact: jsrain@suse.com Found By: --- Blocker: --- libc was updated (security patch today) and no reboot was suggested. A libc update affects the entire system, and it must be rebooted for it to have effect. -- 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=736667 https://bugzilla.novell.com/show_bug.cgi?id=736667#c1 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maintenance@opensuse.org, | |meissner@suse.com AssignedTo|bnc-team-screening@forge.pr |dmueller@suse.com |ovo.novell.com | --- Comment #1 from Marcus Meissner <meissner@suse.com> 2011-12-14 08:18:51 UTC --- it wasnt a security patch, it had some non-security bugfixes. but yes, it should have probably marked RebootNeeded dirk can you still fix this? -- 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=736667 https://bugzilla.novell.com/show_bug.cgi?id=736667#c2 Dirk Mueller <dmueller@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #2 from Dirk Mueller <dmueller@suse.com> 2011-12-16 11:30:51 CET --- there shouldn't be a problem. of course if you want all of the fixes to have effect on everything, you need to reboot, but all newly started applications will already use the new glibc code, and old ones should continue to run. zypper prints a warning with "please run zypper ps to see which services need a restart" and that works just fine for glibc updates as well. The real reason why I also need to wontfix this is that the PackageKit update applet wrongly talks about "Kernel was updated" which is not really the case - glibc is not kernel :-) so we can only set it on kernel updates imho. Anyway, we'll consider to change the reboot_needed flag policy for the next glibc updates, so thanks for pointing this out! -- 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=736667 https://bugzilla.novell.com/show_bug.cgi?id=736667#c3 --- Comment #3 from Carlos Robinson <carlos.e.r@opensuse.org> 2011-12-16 13:33:09 UTC --- Ok. Just for the record, I was using YOU, which says nothing like "zypper ps". I know about it, of course, thus I knew the lot of basic tools that not even an init 1 would reset. -- 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