* Bart Verwilst <email address hidden>:
> If it's indeed a problem in the package, maybe another upgrade would be
> advisable, even if it's just to trigger a restart of the crons..
Well, not via unattended-upgrades, since that just broke :)
> We have 1600 servers that need to have cron restarted now,
If feel your pain!!!
> if we wouldn't be aware of this issue, this could really mess up vital
> parts of our organisation that depend on timed executions.
It did here.
> A new release that restarts cron could make the amount of bad surpises
> over the next couple of days a lot less for a lot of unaware system
> admins.
For all those people who didn't notice their cron not running,
unattended-upgrades won't work!
* Bart Verwilst <email address hidden>:
> If it's indeed a problem in the package, maybe another upgrade would be
> advisable, even if it's just to trigger a restart of the crons..
Well, not via unattended- upgrades, since that just broke :)
> We have 1600 servers that need to have cron restarted now,
If feel your pain!!!
> if we wouldn't be aware of this issue, this could really mess up vital
> parts of our organisation that depend on timed executions.
It did here.
> A new release that restarts cron could make the amount of bad surpises
> over the next couple of days a lot less for a lot of unaware system
> admins.
For all those people who didn't notice their cron not running,
unattended-upgrades won't work!
It's truly FUBARed