On 4/23/2016 9:36 AM, Michael Rasmussen wrote: > On Sat, Apr 23, 2016 at 09:22:25AM -0700, John Jason Jordan wrote: >> The command executed, but this morning I decided to enhance it by >> adding your handy reminder and a couple additional # lines copying and >> pasting your explanation of '-auf' for future reference. When I went to >> save my crontab to disk (Crtl-o in nano) I noticed from the prompt that >> nano wanted to write the file as: >> >> /tmp/crontab.2Atvun/crontab >> >> This puzzles me. I thought things in /tmp were only for temporary use. >> Why is the file saved to /tmp? Shouldn't it be saved to someplace in ~/? > the command `crontab -e` creates a copy of your crontab file in /tmp. > After you complete your editing and save it the crontab program checks it for > validity before copying the version in /tmp to the real crontab - in your > example > it is probably /var/spool/cron/jjj or /var/spool/cron/crontabs/jjj > > No, not in ~/ the folks who created cron decided that all cron files on a > system > should be stored in the same place.
In a true NFS environment, you would almost certainly not want your crontab kept in $HOME. Consider an network with ~100 work- stations and a single NFS server providing $HOME for the entire userbase. When you schedule a task for 3pm, which one of the 100+ systems should run that job? This is why job scheduling is managed on a local filesystems (e.g. /var, /etc, ...). _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
