On Tue, Feb 29, 2000 at 05:30:07PM -0500, Ben Collins wrote:
> On Tue, Feb 29, 2000 at 02:32:41PM -0800, Ernest Johanson wrote:
> > I had a similar experience recently on the alpha platform. If I added
> > something to the crontab file, it didn't run. I had to stop and start the
> > cron daemon to get the new entry to run. Reloading didn't do it. This is
> > on frozen.
> >
> > Ernest Johanson
> > Web Systems Administrator
> > Fuller Theological Seminary
> >
> >
> > On Tue, 29 Feb 2000 kmself@ix.netcom.com wrote:
> >
> > > Date: Tue, 29 Feb 2000 10:33:01 -0800
> > > From: kmself@ix.netcom.com
> > > To: debian-user <debian-user@lists.debian.org>
> > > Subject: cron.daily isn't
> > >
> > > I seem to have a problem with my anacron. In particular, cron.daily
> > > scripts don't appear to run when advertised, or more troubling, at all.
> > >
> > > Both cron and at are doing fine.
>
> If your system is up 24/7, I suggest removing at. It is only meant for
> machines that are up "sometimes, like dual boot setups, desktops that get
> shutdown at night, etc...
>
> If it still occurs (or doesn't as the case may be), then perhaps at is at
> fault somehow. I've never heard of problems with cron.
s/at/anachron ?
'at' is a very useful one-time scheduler. I use it frequently as an
alternative to backgrounding stuff, say:
echo "apt-get update " | at now
...with results mailed to myself. It's convenient.
Yes, I do have anacron on this machine. Though in the case of both
cron and anacron, it's run-parts which is being invoked to run the
various cron.daily scripts.
As best I can tell, various of the scripts may be hanging or going
zombie on me. anacron may not want to run a second process when the
first is still active. Need to look into it.
--
Karsten M. Self (kmself@ix.netcom.com)
What part of "Gestalt" don't you understand?
Scope out Scoop: http://scoop.kuro5hin.org/
Nothin' rusty about Kuro5hin: http://www.kuro5hin.org/
