https://bugzilla.novell.com/show_bug.cgi?id=540587 https://bugzilla.novell.com/show_bug.cgi?id=540587#c24 --- Comment #24 from L. A. Walsh <suse@tlinx.org> 2014-01-16 15:33:34 PST --- Re: Based on comment #19 reassigning to bugowner of squid.... I don't feel good about that -- since EACH component that is part of the source stream is vulnerable. New network driver? do you unload and reload net driver? Or bring it down and restart it? What about cifs/nfs drivers -- or a "fuser" based file system relying on a user space daemon. If I was running through dante/socks, same thing. If I am running through a sshfs or just "ssh"... they shouldn't be restarted eitehr (or rsh if that was used)... Saying squid has a problem (and it may), puts the onus on each tool -- maybe the scripts that do "service restarts" should be put at the end of an entire update? AND -- take a note from Windows:: The old versions of files may remain in use until you reboot the system. To see files using deleted versions press <xxx> or use <zypper command>... Reboot now or later? [later] -- 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.