Re: cron.daily isn't
On Thu, Mar 02, 2000 at 10:25:42PM +1100, Damon Muller wrote
> Quoth email@example.com,
> > 'at' is a very useful one-time scheduler. I use it frequently as an
> > alternative to backgrounding stuff, say:
> When my clock-radio broke recently, I started using at as an alarm
> clock, setting it to play MP3s for me in the morning to wake me up (my
> schedule isn't regular enough to warrant a cron job). Now if only they
> could make at with a snooze button... :)
> > 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.
> I also have a problem on a slink system with a (at least one) cron.daily
> job not running. It's a logcheck script, and runs fine when strated from
> a shell prompt. There is no evidence anywhere what is going on - nothing
> in the logs and nothing being mailed to me. All the paths and everything
> are set in the script correctly, and I can't for the life of me work out
> what the problem is.
> I even tried adding `touch /var/tmp/blah' at the start of the file
> (right after #!/bin/sh', but there is still no evidence it's running.
This doesn't seem to be the original poster's problem, but run-parts
(which invokes the various scripts in /etc/cron.daily, /etc/ppp/ip-up.d,
/etc/rc2.d, etc. etc.) has its own requirements for how scripts are
named - for instance, it won't run /etc/cron.d/my-script.sh.
Quoting the man page:
run-parts runs a number of scripts or programs found in a
single directory directory. Filenames should consist
entirely of upper and lower case letters, digits, under-
scores, and hyphens. Subdirectories of directory and
files with other names will be silently ignored.
Scripts must follow the #!/bin/interpretername convention
in order to be executed. They will not automatically be
executed by /bin/sh.
"Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark