Trouble-shooting Cron Problems FreeBSD5.4

2006-10-31 Thread Martin McCormick
After building a new FreeBSD5.4 system, I have done something bad to it. When cron runs jobs in /etc/crontab as operator, it seems as if that 6TH field in /etc/crontab is being interpreted as a command rather than the user ID it is supposed to run under. I keep getting messages

Re: Trouble-shooting Cron Problems FreeBSD5.4

2006-10-31 Thread Lane
On Tuesday 31 October 2006 12:08, Martin McCormick wrote: After building a new FreeBSD5.4 system, I have done something bad to it. When cron runs jobs in /etc/crontab as operator, it seems as if that 6TH field in /etc/crontab is being interpreted as a command rather than the user

Re: Trouble-shooting Cron Problems FreeBSD5.4

2006-10-31 Thread Dan Nelson
In the last episode (Oct 31), Martin McCormick said: After building a new FreeBSD5.4 system, I have done something bad to it. When cron runs jobs in /etc/crontab as operator, it seems as if that 6TH field in /etc/crontab is being interpreted as a command rather than the user ID

Re: Trouble-shooting Cron Problems FreeBSD5.4

2006-10-31 Thread Martin McCormick
Dan Nelson writes: The operator user has no access to /etc/crontab. You have probably copied entries from the system crontab (i.e. /etc/crontab) into a user's crontab. The system crontab has the extra user column, where user crontabs don't (since they always run as the user).