Crontab blown away

My crontab was completely obliterated by the latest OS upgrade. And I can’t seem to save a new one. Anyone else having this problem??

–Brad Barkhouse
Be a Contender!

If you’re on atomic, there was a problem with the cron spool getting hosed during the upgrade process. I believe this was the only machine affected by that problem.

There was also an MTA configuration problem which prevented mail from being sent out (although it was queued on the server).

I sent an announcement about both of these problems just now.

Er, how about ‘fud’? crontab -l and -e returned nil just now (although my last job ran this morning as expected)