Hi Rafael, >> How is it possible that one system will not see the update until last >> night when I have been running the update cycle each night and all my >> systems use the same uplink? > > >From the log: > >> Preparing to replace libssl1.0.0:amd64 1.0.1e-2+deb7u6 (using >> .../libssl1.0.0_1.0.1e-2+deb7u7_amd64.deb) > > You were upgrading to the version that I just released last night - perhaps > the other machines ran apt-get update before it was released so they didn't > see it.
Aha, I assumed this was the same ssl upgrade I had seen on my other systems last week. I now see this is the upgrade from deb7u6 to deb7u7. >> --------------------- >> Why did the apt-get update NOT restart the services? How can I find out? > > Services are never automatically restarted due to library updates, you need > to do that by hand. Some times, restarting services might be proposed. Ok, I assumes the restarts were allways done as last week several ssl upgrades did service restarts for me. > The message in the log is just libssl1.0.0 checking for services that might > need to be restarted to get the Heartbleed bugfix applied. Had it found any, > it would have proposed you to restart them. But that is funy because the checkrestart command that I issued right after found several services that needed restarting. But maybe they did not need a restart just for hartbleed? Bonno Bloksma -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/89d1798a7351d040b4e74e0a043c69d786190...@hglexch-01.tio.nl
