Re: Trouble-shooting Cron Problems FreeBSD5.4
- From: Lane <lane@xxxxxxxxxxxxxx>
- Date: Tue, 31 Oct 2006 13:29:04 -0500
On Tuesday 31 October 2006 12:08, Martin McCormick wrote:
After building a new FreeBSD5.4 system, I have doneMartin,
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 like:
From: operator@xxxxxxxxxxxxxxxxx (Cron Daemon)
Subject: Cron <operator@system> root newsyslog
root: not found
Comparing this system with another properly-functioning
5.4 system has, as of yet, shown nothing unusual. If I become
root and manually run the job in question, it runs without a
complaint.
The crontab file on the problem system is an exact copy
of the crontab file on the working system. Both crons appear to
be running with the same flags as in
465 ?? Ss 3:24.39 /usr/sbin/cron -s
Any suggestions as to what I should look at next? Both
systems' crons are showing the same environments if I make them
run the env command. Many thanks.
Martin McCormick WB5AGZ Stillwater, OK
Systems Engineer
OSU Information Technology Department Network Operations Group
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
Post the offending line or even all of /etc/crontab
lane
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"
- References:
- Trouble-shooting Cron Problems FreeBSD5.4
- From: Martin McCormick
- Trouble-shooting Cron Problems FreeBSD5.4
- Prev by Date: Trouble-shooting Cron Problems FreeBSD5.4
- Next by Date: Re: Trouble-shooting Cron Problems FreeBSD5.4
- Previous by thread: Trouble-shooting Cron Problems FreeBSD5.4
- Next by thread: Re: Trouble-shooting Cron Problems FreeBSD5.4
- Index(es):
Relevant Pages
|
|