First of all, apologies to all for the thread hijack--I should have checked if there was a reference header... At this point, it's probably not useful for me to go back and try and fix this. My /etc/crontab is a carbon copy of yours, down to the permissions, so I have a hard time believing that's the issue. Will check out the cron.d directory, but last time I checked it was empty. Thanks for the help, though. Anyone recognize what condition would cause the error I'm seeing in the logs? Mike On Fri, August 20, 2004 10:56 am, Robert Locke said: > Mike, > > Be careful, you hijacked a thread by replying to an existing message and > just changing the topic (there are internal tags that aid in threading). > > I seem to have the same set of cron packages, so I can only assume that > perhaps there is a problem in your /etc/crontab file... Here is mine as > an example (it's the default): > > # cat /etc/crontab > SHELL=/bin/bash > PATH=/sbin:/bin:/usr/sbin:/usr/bin > MAILTO=root > HOME=/ > > # run-parts > 01 * * * * root run-parts /etc/cron.hourly > 02 4 * * * root run-parts /etc/cron.daily > 22 4 * * 0 root run-parts /etc/cron.weekly > 42 4 1 * * root run-parts /etc/cron.monthly > > The other place I just thought of looking is that crond will also hunt > through the directory /etc/cron.d, so perhaps there is an extraneous > file there with a bad format (files should have the same format as the > /etc/crontab). > > Also, not that permissions should get in the way but: > # ls -l /etc/crontab > -rw-r--r-- 1 root root 255 Feb 15 2004 /etc/crontab > > HTH a little, > > --Rob > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list >