Lines Matching refs:crontab

5 --	Environment variables can be set in each crontab.  SHELL, USER,
7 	USER can be changed in the crontab.  PATH is especially useful to
28 	person that cron mails the output of commands in that crontab.  This is
44 --	Each user gets their own crontab file.  This is a win over BSD 4.2,
45 	where only root has one, and over BSD 4.3, where they made the crontab
47 	uid's, root is still the only one who can edit the crontab file.  This
50 --	The 'crontab' command is loosely compatible with SysV, but has more
51 	options which just generally make more sense.  Running crontab with
54 --	Comments and blank lines are allowed in the crontab file.  Comments
58 --	(big win) If the `crontab' command changes anything in any crontab,
61 	daemon whenever you change a crontab.  In other crons, the crontab
64 --	In order to support the automatic reload, the crontab files are not
65 	readable or writable except by 'crontab' or 'cron'.  This is not a
66 	problem, since 'crontab' will let you do pretty much whatever you
67 	want to your own crontab, or if you are root, to anybody's crontab.
70 	be mailed to the owner of the crontab that contained the command (or