09-20-2016, 03:16 AM
Thanks for taking the time to clarify, Jerry! 
I came across /etc/update-motd.d/ and /usr/lib/update-notifier/ when I was following up my discovery of update notifications displayed when I remotely logged in to one of my systems on the command line.
I haven't dug deeper into it (yet) to understand the full setup.
You mention that the apt-check is run at boot time.
Just had a quick look at cron jobs and found apt-compat as a daily one pointing to /usr/lib/apt/apt.systemd.daily.
So I hope I'm not wrong to assume that an update is not only run at boot/reboot time but on a regular basis.
Otherwise there wouldn't be a check for quite some time considering that people just suspend their system. Also the execpi loop in the widget would just use up resources without real benefit.
Also, I'm still not clear about the effects of the settings in Synaptic -> Settings -> Software & Updates -> Updates, especially in Linux Lite.
Looking into the setup/configuration of (semi)automatic updates seems like opening a can of worms ...

I came across /etc/update-motd.d/ and /usr/lib/update-notifier/ when I was following up my discovery of update notifications displayed when I remotely logged in to one of my systems on the command line.
I haven't dug deeper into it (yet) to understand the full setup.
You mention that the apt-check is run at boot time.
Just had a quick look at cron jobs and found apt-compat as a daily one pointing to /usr/lib/apt/apt.systemd.daily.
So I hope I'm not wrong to assume that an update is not only run at boot/reboot time but on a regular basis.
Otherwise there wouldn't be a check for quite some time considering that people just suspend their system. Also the execpi loop in the widget would just use up resources without real benefit.
Also, I'm still not clear about the effects of the settings in Synaptic -> Settings -> Software & Updates -> Updates, especially in Linux Lite.
Looking into the setup/configuration of (semi)automatic updates seems like opening a can of worms ...
