With respect to "unattended-upgrades blocking other cron.daily scripts via shutdown -r" I reflected:

Now what would a "correct" or "better" behavior be?

I suggest to trigger an asynchronous shutdown, that is *not*
to wait for `shutdown -r $TIME` to come back so that whatever
daily menial taks are scheduled via /etc/cron.daily are able
to be executed.

What about the idea of using

    echo "shutdown -r now" | at $TIME

instead of directly calling

    shutdown -r now

Pro:

* async execution. unattended-update can finish it's stuff and
  the rest of cron.daily finishes correctly
* consoles won't be flooded with repeat "Systeme will be going
  doing in XX hours"

Con:

* does care have to be taken that unattended-upgrade won't re-run
  while it wants the system to reboot?
* behavior change (this should be triggering a major semver change...)
  * this could be worked around with yet another config option
    (UseAtInstead=True)
* users on the system won't be warned of the system going down in
  XX hours

What do you think?
*t

Reply via email to