That's what I thought, but I don't think the security update mentions that. Shouldn't it be mentioned somewhere?
IIRC some updates also offered to restart affected services semi-automatically, why was that not the case with this update? On Sat, Jan 31, 2015 at 11:14 AM, Aurelien Jarno <[email protected]> wrote: > On 2015-01-27 23:40, Olaf van der Spek wrote: >> Hi, >> >> It seems no services were restarted after the recent update. Shouldn't >> this be done to ensure the updated code is picked up? > > As glibc is used by virtually all the code running on a machine, it > means that everything might need to be restarted. Rebooting the machine > looks the easiest way to do that, even if not really convenient. > > -- > Aurelien Jarno GPG: 4096R/1DDD8C9B > [email protected] http://www.aurel32.net -- Olaf -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/caa7u3hmqm0ne6uvnsn9r7wu0odaaprus4tarxg_c8kp18g3...@mail.gmail.com
