On Thu, 2017-09-07 at 11:00 -0400, Matthew Miller wrote: > [ ... ] > Note also that in the event of security problems, you may still have > stuff running with the old versions in memory. Run `sudo dnf > needs-restarting` to see what needs to restart; often a reboot is just > _easier_. Easier, yes, and probably simply the only option in instances where services needing a restart simply cannot be restarted after an upgrade, except by a full reboot. That's what just happened here, an hour ago: I did an upgrade on a tmux session, on a tty - quite a few packages got upgraded, glibc among them. After the upgrade, and after restarting gdm, (something like systemctl restart gdm, IIRC), after re-logged in to Gnome still I got this from dnf needs-restarting: ================================= 1 : /usr/lib/systemd/systemd --system --deserialize 17 3720 : /usr/lib/systemd/systemd-udevd 3916 : /sbin/auditd 3946 : /usr/libexec/accounts-daemon 3957 : /usr/lib/systemd/systemd-logind 3958 : /usr/sbin/abrtd -d -s 3972 : /usr/sbin/gssproxy -D 3999 : /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid 4010 : /usr/lib/polkit-1/polkitd --no-debug 4030 : /usr/sbin/NetworkManager --no-daemon 4047 : /usr/sbin/libvirtd 4227 : /usr/libexec/bluetooth/bluetoothd 4295 : /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper 4375 : /usr/bin/abrt-dump-journal-xorg -fxtD 4376 : /usr/bin/abrt-dump-journal-oops -fxtD 4377 : /usr/bin/abrt-dump-journal-core -D -T -f -e 4411 : /usr/libexec/upowerd 4447 : /usr/bin/pulseaudio --start --log-target=syslog 4495 : /usr/libexec/packagekitd 4578 : /usr/libexec/colord 5084 : /usr/libexec/udisks2/udisksd 5436 : /usr/sbin/cupsd -l 5650 : /usr/libexec/fwupd/fwupd 7493 : /sbin/agetty --noclear tty3 linux 18667 : /usr/sbin/crond -n 19027 : /usr/bin/python3 -Es /usr/sbin/setroubleshootd -f 27522 : /sbin/agetty --noclear tty5 linux 27538 : /sbin/agetty --noclear tty6 linux ================================================== Please note systemd-udevd, 3720, on top of the list: seems to be the kernel device manager, so I think it was good reason for a reboot, because how do you restart a "static" service like systemd-udevd? After a full reboot then, 'dnf needs-restarting' now yields nothing. I can't say I'm happy with this situation, but at least - I think - I now know how to handle it. Thanks a lot to everyone in this thread: you definitely helped a lot! Best Regards Wolfgang _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
