Hiho...
Javier Fernández-Sanguino Peña schrieb:
Can you attach to the children cron process with gdb, run it and then
show me the output of running 'bt' from gdb?
Hm, that didn't help much...
Not only are there no debugging symbols in the cron child, but I
apparently triggered a bug in gdb,
Hiho!
As I suspected the bug occured again after I updated my system with aptitude.
I scheduled an additional cronjob at 13:45:
# One additional for debugging
45 13 * * * /home/friedel/bin/fetchstuff
And started the strace:
[EMAIL PROTECTED]:~# strace -f -p `pidof cron` 2strace.cron
At
On Sat, Dec 03, 2005 at 01:52:30PM +0100, Friedrich Delgado Friedrichs wrote:
Hiho!
As I suspected the bug occured again after I updated my system with aptitude.
Strange..
At 13:45:01 cron tried to start the cronjob and the child process received
a segmentation fault.
The segmentation
Javier Fernández-Sanguino Peña schrieb:
Hm...
As I suspected the bug occured again after I updated my system with
aptitude.
Strange..
I am not so sure of this connection any more... I just restarted cron
by accident (while trying to attach a debugger to it, because I
couldn't think of a
Package: cron
Version: 3.0pl1-93
Followup-For: Bug #260789
Hi!
I see very similar phenomena to what the OP reported. Cronjobs from
personal crontabs are not executed.
On my machine it started after an aptitude system upgrade in the
vicinity of a daylight saving time switch (well, maybe two
On Wed, Nov 30, 2005 at 09:05:54AM +0100, Friedrich Delgado Friedrichs wrote:
Package: cron
Version: 3.0pl1-93
Followup-For: Bug #260789
Hi!
I see very similar phenomena to what the OP reported. Cronjobs from
personal crontabs are not executed.
(...)
Cronjobs do not run, although cron
Javier Fernández-Sanguino Peña schrieb:
- show me what is returned by
# ls -la /var/spool/cron/crontabs
[EMAIL PROTECTED]:~# ls -la /var/spool/cron/crontabs
total 16
drwx-wx--T 2 rootcrontab 4096 Nov 30 09:03 .
drwxr-xr-x 5 rootroot4096 Feb 25 2002 ..
-rw--- 1 friedel crontab
7 matches
Mail list logo
