On 01/04/12 18:02, emijrp wrote:
Yes, probably it was on nightshade. Why weren't they copied to the new server?
Because hardware problems don't usually warn?
That said, I hope we could better manage crontabs in the future.
I take for granted that the debian installs will have only cronie as crontab, but I also wonder if they could be moved to the /home, so they are stored and backed up there with all the rest of the user data, instead of having one file per server at a different location. They could for instance live at $HOME/crontabs/crontab and $HOME/crontabs/jobs
Such crontabs wouldn't run when the /home is not available, but it doesn't seem a big issue, given that most scripts would need some kind of fs access.
Looking at cronie source, it seems that it would perfectly work if the files at /var/spool/cron contained symlinks instead of files and is indeed documented in crontab(5). Combined with its clustering support, such setup should work.