freebsd stable - Mar 2005 - Abort Trap for cron-jobs in 5.3

Hi all,
I've got four servers that all have the same problem: when jobs get
started from Cron, they die after some time with an "Abort trap". Jobs
that are dying are:

/usr/libexec/atrun >> /var/log/cron 2>&1
/usr/bin/nice -10 /usr/local/bin/zsh /root/bin/sendBarkMail.sh > /dev/null
2>&1

I also get this on virtually every shell-script that uses tar, leaving my
filesystem littered with bsdtar.core files.

Running these jobs from the command prompt works fine. Any suggestions on
what may be causing them to die from cron? sendBarkMail.sh simply moves
mails from one folder to another periodically

Cheers

	Nik

Note to self: ask the question. ;-)

What I'm wondering about is: what could be causing the Abort Trap's?

World and kernel are a recent RELENG_5_3 compiled like described in
src/UPDATING.

Cheers

	Nik

On Tue, 15 Mar 2005, Niklas Saers wrote:
> Hi all,
> I've got four servers that all have the same problem: when jobs get
> started from Cron, they die after some time with an "Abort trap".
Jobs
> that are dying are:
>
> /usr/libexec/atrun >> /var/log/cron 2>&1
> /usr/bin/nice -10 /usr/local/bin/zsh /root/bin/sendBarkMail.sh >
/dev/null 2>&1
>
> I also get this on virtually every shell-script that uses tar, leaving my
> filesystem littered with bsdtar.core files.
>
> Running these jobs from the command prompt works fine. Any suggestions on
> what may be causing them to die from cron? sendBarkMail.sh simply moves
> mails from one folder to another periodically
>
> Cheers
>
> 	Nik
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"
>