Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!sol.ctr.columbia.edu!caen!sdd.hp.com!spool.mu.edu!uunet!sfs!jmp
From: jmp@sfs.uucp (John Pearce)
Newsgroups: comp.unix.xenix.sco
Subject: Re: Cron problems
Message-ID: <1991Feb27.192722.24286@sfs.uucp>
Date: 27 Feb 91 19:27:22 GMT
References: <201798@hrc.UUCP> <973@pallas.athenanet.com> <1991Feb23.184255.26348@jpradley.jpr.com> <999@pallas.athenanet.com>
Reply-To: jmp@sfs.UUCP (John Pearce)
Organization: Suncoast Fire and Safety Equipment, Inc. -- Sarasota, Florida
Lines: 20

>Actually with Xenix 386, 2.2.3, every 6 hours is not enough.  I have had
>cron go to sleep with idle spans as short as 3 hours.
>The recommendation from SCO is once an HOUR.

I experienced this problem at about the time this thread started, and
execution of /bin/true from cron once an hour _seems_ to have solved my
crontabs problems.

However, both 'at' and 'batch' seem now to have gone to sleep.  Commands 
deposited in either of them sit there until removed.

Is this a problem anyone has experienced, and is it related _directly_ 
to the cron question?  Does anyone have a fix?

I am running SCO Xenix 2.3.1.
-- 
============================================================================
John M. Pearce +++ Suncoast Fire and Safety Equipment, Inc. +++ Sarasota, FL
jmp@sfs               (813) 955-2202  Fax (813) 954-4213       uunet!sfs!jmp
============================================================================