Re: [PLUG] Ubuntu Debian updates/ rebooting question

I'm more of a RHEL user on servers but here's my 2c.

In addition to what others have stated (kernel and dbus) I've found that glibc usually requires a reboot as well since so many things depend on it.

Here's a good tip for what services need to be restarted after a non-reboot update....

https://github.com/sag47/drexel-university/blob/master/bin/wasted-ram-updates.py

I use that to determine which services must be bounced. You should read the full comment doc at the top of the script to understand its intended purpose. I would also recommend reviewing the source code so that you understand in more detail exactly what the script is doing.

It can be noted that a lot of times you can use a combination of "lsof | grep deleted" and the "cat /proc/PID/cmdline" or "cat /proc/PID/comm" file to determine that without using the script. The script definitely makes it easier though.

SAM

On Thu, Jun 27, 2013 at 2:41 PM, Andrew Libby <alibby@xforty.com> wrote:

Good thoughts and Info, thanks Chad.

Andy

On 6/27/13 1:17 PM, Chad Waters wrote:
> The Ubuntu Security Announce list details what requires a
> reboot:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce
>
> kernel:
> http://www.ubuntu.com/usn/usn-1878-1/
>
> dbus:
> http://www.ubuntu.com/usn/usn-1874-1/
>
> Its should be more than what requires a reboot though: what
> package upgrades are going to affect the applications and
> services that run on a specific machine? I don't think you
> can script that.
>
> These packages might be of interest:
> apt-listchanges
> apt-listbugs (I think this is in the ubuntu repos(?), I'm a
> more of a Debian user)
>
>
>
> On Thu, Jun 27, 2013 at 11:24 AM, Andrew Libby

> <alibby@xforty.com <mailto:alibby@xforty.com>> wrote:
>
>
> Hi Folks,
>
> I manage a number of ubuntu systems for customers. We apply
> updates, review logs, deal with incidents, yadda yadda.
>
> So when informing a customer that we're going to apply some
> updates, I'd like to be able to tell them ahead of time
> if the updates will require a reboot. I'm hoping I'm
> missing something simple, but it does not seem straight
> forward.
>
> Here's what I've come up with:
>
> sudo apt-get update
> sudo apt-get --download-only upgrade
>
> For each of the packages listed under
>
> "The following packages will be upgraded:"
>
> dpkg-deb --control package-name
>
> grep -rn notify-reboot-required DEBIAN
>
> Essentially, if anything in the control area
> of the package contains notify-reboot-required, it's
> likely to touch /var/run/reboot-required.
>
> Their an easier method to tell ahead of time that anyone
> knows?
>
> Thanks,
>
> Andy
>
> --
>
> Andrew Libby
> xforty technologies
> http://xforty.com

> alibby@xforty.com <mailto:alibby@xforty.com>

>
> ___________________________________________________________________________
> Philadelphia Linux Users Group --
> http://www.phillylinux.org
> Announcements -
> http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion --
> http://lists.phillylinux.org/mailman/listinfo/plug
>
>
>
>
> ___________________________________________________________________________
> Philadelphia Linux Users Group -- http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
>

--

Andrew Libby
xforty technologies
http://xforty.com
alibby@xforty.com

484-887-7505 x 1115

___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug