Mailinglist Archive: opensuse (3336 mails)

< Previous Next >
Re: [SLE] Mysterious cron problem with Suse 9.3
  • From: Ken Schneider <suse-list@xxxxxxxxxxxxx>
  • Date: Fri, 02 Dec 2005 13:47:47 -0500
  • Message-id: <1133549267.1470.18.camel@xxxxxxxxxxxxxxxxx>
On Fri, 2005-12-02 at 13:40 -0500, Ken Schneider wrote:
> On Fri, 2005-12-02 at 13:22 -0500, Eric E wrote:
> > Hi all,
> > I'm running Suse Linux 9.3, and I'm having problems with cron not
> > actually running cron jobs. I suspect this is the kind of profile issue
> > that commonly happens with cron jobs, but I don't have any idea how to
> > debug it.
> >
> > For example, if as root, I run crontab -e and enter the following very
> > simple cron job:
> >
> > 22 12 * * * /usr/bin/touch /root/hello.root
> >
> > In /var/log/messages, I have the following output:
> >
> > Dec 2 12:21:23 hypervisor1 crontab[7015]: (root) BEGIN EDIT (root)
> > Dec 2 12:21:25 hypervisor1 crontab[7015]: (root) REPLACE (root)
> > Dec 2 12:21:25 hypervisor1 crontab[7015]: (root) END EDIT (root)
> > Dec 2 12:22:01 hypervisor1 /usr/sbin/cron[6536]: (root) RELOAD (tabs/root)
> >
> > so it sure seems like cron is waking up, finding the job, and then going
> > back to sleep. However, the file that should be touch-ed
> > is not there, and there are no error messages, either in
> > /var/log/messages or as an email.
> >
> > Can anyone give me advice on how to debug this problem, or why cron does
> > not appear to be actually running the job?
> >
> > Thanks,
> >
> > Eric
> >
> >
> The touch command is in /bin not /usr/bin. To verify use which touch to
> find where it is on your system. On my 9.3 system it is under /bin.
>
Correction. There is also a link in /usr/bin. Sorry. But I will agree
with Bruce that you set the time to run to close to the clock time. Try
setting it 2-3 minutes in the future to test.

--
Ken Schneider
UNIX since 1989, linux since 1994, SuSE since 1998


< Previous Next >
References