On Mon, Jul 16, 2001 at 06:00:01PM +0200, Chojin wrote:
> > cd /usr/src/usr.sbin/cron
> > make cleandir depend
> > make CFLAGS="-ggdb -g3" STRIP="" all install
> >
> > ..then run '/usr/sbin/cron' from the command line, and see if it
> > leaves a coredump in the current directory. If it does, then
> > do the following:
> >
> > gdb /usr/sbin/cron /path/to/cron.core
> > (at the gdb prompt)
> > bt
> > info local
> > up
> > info local
> > up
> > info local
> > [repeat until highest level]
> >
> > Hm. Now that I kinda tested this, cron doesn't seem to leave
> > a corefile. Well, still.. this message was redirected to -stable
> > in the hope that somebody there would know better how to help :\
> >
> > G'luck,
> > Peter
> >
> > --
> > This sentence claims to be an Epimenides paradox, but it is lying.
> >
>
> Okay, I followed your instructions:
(I purposefully redirected this to -stable.. since you don't want
to acknowledge it is a -stable issue, staying on -hackers this time..)
The stack trace you posted seems to imply that cron is dying while
processing rico's crontab, and is dying at such a point in the code
that would indicate that rico's account has expired. Is that the case?
If so, then the easiest thing for you to do would be to remove rico's
crontab (crontab -u rico -l > rico.cron.save && crontab -u rico -r)
until rico's account is reactivated or totally removed.
G'luck,
Peter
--
.siht ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
