4th November 2016, 4:53
Thank you. Would this be an appropriate self-management paradigm then [ie, for me, on a home Tower for recreation, not a server]?
1. Do routine updates as normal.
2. Glance at the CD Logout applet to see if it's whingeing again to reboot.
3. If it is, inspect reboot-required.pkgs & assess if anything there is "critical".
4. If critical, sigh deeply, close all my docs & pgms, reboot.
5. If not critical, try to ignore that nagging applet, & plan a reboot some other, more convenient, time.
Ironically, having done that nagged reboot last night, then reopened all my working docs & pgms, spread across my 9 VDs in the sequence i like, this morning Update Manager has another 5 updates for me. Hilariously, one is called "update-notifier"!!
1. Do routine updates as normal.
2. Glance at the CD Logout applet to see if it's whingeing again to reboot.
3. If it is, inspect reboot-required.pkgs & assess if anything there is "critical".
4. If critical, sigh deeply, close all my docs & pgms, reboot.
5. If not critical, try to ignore that nagging applet, & plan a reboot some other, more convenient, time.
Ironically, having done that nagged reboot last night, then reopened all my working docs & pgms, spread across my 9 VDs in the sequence i like, this morning Update Manager has another 5 updates for me. Hilariously, one is called "update-notifier"!!