From owner-freebsd-hackers Mon Jul 16 10:42:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 3549E37B401 for ; Mon, 16 Jul 2001 10:42:39 -0700 (PDT) (envelope-from freebsd@tarakan-network.com) Received: from chojin (chojin [192.168.69.2]) by tarakan-network.com (8.11.4/8.11.3) with SMTP id f6GHgS827661; Mon, 16 Jul 2001 19:42:29 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <001b01c10e1e$a9bf9f80$0245a8c0@chojin> From: "Chojin" To: "Peter Pentchev" Cc: References: <007001c10e0c$f02d94c0$0245a8c0@chojin> <20010716185318.E56285@ringworld.oblivion.bg> <002101c10e10$5edea640$0245a8c0@chojin> <20010716193956.H56285@ringworld.oblivion.bg> Subject: Re: Cron program core dumped (signal 11) Date: Mon, 16 Jul 2001 19:42:14 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In fact, rico account has expired. I removed expiration ,then now cron works. But I thought cron had no problem if an account expires. Strange... :p Thanks for all. Regards. Chojin ----- Original Message ----- From: "Peter Pentchev" To: "Chojin" Cc: Sent: Monday, July 16, 2001 6:39 PM Subject: Re: Cron program core dumped (signal 11) > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message