Aleksej([EMAIL PROTECTED]) is reported to have said:
> Wayne Topa wrote:
>
> > Has anyone, running etch or sid, noticed a problem with cron
> > _not_ running jobs in /etc/crontab?
>
>
> Just over an hour ago.
>
> > I had Upgraded on Aug 28 to icron_3.0pl1-95 and cron has not run since.
>
>
>
Wayne Topa wrote:
> Has anyone, running etch or sid, noticed a problem with cron
> _not_ running jobs in /etc/crontab?
Just over an hour ago.
> I had Upgraded on Aug 28 to icron_3.0pl1-95 and cron has not run since.
Etch, -95; don't know when I upgraded it.
Nothing in the logs about that, it
Has anyone, running etch or sid, noticed a problem with cron
_not_ running jobs in /etc/crontab?
My mail was not being picked up and when I checked I found that
cron had stopped running jobs in /etc/crontab.
I had Upgraded on Aug 28 to icron_3.0pl1-95 and cron has not run since.
cron_3.0pl1-94_i
Has anyone, running etch or sid, noticed a problem with cron
_not_ running jobs in /etc/crontab?
My mail was not being picked up and when I checked I found that
cron had stopped running jobs in /etc/crontab.
I had Upgraded on Aug 28 to icron_3.0pl1-95 and cron has not run since.
cron_3.0pl1-94_i
Christopher Pharo Glæserud,
> Out of the blue, cron has suddenly stopped working, and all I get in my
> logs (syslog) is:
>
> CRON[4008]: Critical error - immediate abort
For the interrested:
Problem solved. Apparently libpam-modules version 0.79-2 is what broke
cron. Updated to 0.79-3 and cro
Out of the blue, cron has suddenly stopped working, and all I get in my
logs (syslog) is:
CRON[4008]: Critical error - immediate abort
where 4008 is the pid of the child that the cron daemon forks.
I'ts been like this since Oct 1, 15:00 CET. I'm running sid, but there
hasn't been any recent chang
On Mon, Sep 08, 2003 at 11:42:50AM -0700, Curtis Spencer wrote:
| I put a small script into the cron.daily folder expecting it to run.
[...]
| My little script cron_test.pl is installed with 755 privileges in
$ man run-parts
The script won't be run as long as the name has a '.' in it.
(there are
I put a small script into the cron.daily folder expecting it to run. It
simply creates a file with the current timestamp as its name to see if
successfully ran. However, I woke up this morning to not be greeted by
this file, so I know cron didn't run it. I did check my root email to
find the
> Hi. I have problems wih cron from the testing archives. When I edit a
crontab
> file with `crontab -e', I must restart cron before the changes are applied
> (This means that I must `killall cron ; cron' before it works). I find
this to
> be *VERY* annoying, and I was wondering if any of you ha
Hi. I have problems wih cron from the testing archives. When I edit a crontab
file with `crontab -e', I must restart cron before the changes are applied
(This means that I must `killall cron ; cron' before it works). I find this to
be *VERY* annoying, and I was wondering if any of you had had s
Has anyone else had problems with cron since version cron_3.0pl1-45.deb was
installed into hamm ?
The following error messages from crom were in my mailbox this morning.
Subject :Cron <[EMAIL PROTECTED]> root run-parts --report /etc/cron.daily
Message body : /bin/sh: root: command not found
11 matches
Mail list logo
