This is certainly not a glibc "bug", but perhaps something that required better documentation. As stated previously, the restart code you see has nothing to do with security updates, but is to make sure that various services don't explode on major version upgrades.
The reality, though, is that every time you perform a security update of a library (any library, this isn't libc-specific), you might want to restart the daemons linked to it. Now, in many cases, this will be handled in time by logrotate cronjobs restarting things, and other such mechanisms, but not everything restarts itself over time. Again, I think this is a user education (and, hence, documentation) issue. Prompting people to reboot after ever single upgrade is heavy- handed and unnecessary (and dilutes the severity when we tell you that really DO need to reboot), but people should be aware of what's going on, if they read a bit. (All of the above said, it might be kinda slick for upstart to have a dpkg trigger that could walk "libraries installed in the last dpkg run", compare against "processes currently running and linked to those libraries that I know how to restart" and bounce the ones that have upstart jobs) -- libc security update does not trigger apache (and others) to be restarted https://bugs.launchpad.net/bugs/587982 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
