From owner-freebsd-stable Sat Jul 14 7:11: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from panda.freebsdsystems.com (panda.freebsdsystems.com [216.126.95.28]) by hub.freebsd.org (Postfix) with SMTP id 12B7337B401 for ; Sat, 14 Jul 2001 07:10:56 -0700 (PDT) (envelope-from lnb@freebsdsystems.com) Received: (qmail 3700 invoked by uid 0); 14 Jul 2001 14:10:54 -0000 Received: from pm3-tor-56k-95.tht.net (HELO noemie) (216.126.89.95) by panda.freebsdsystems.com with SMTP; 14 Jul 2001 14:10:54 -0000 From: "Lanny Baron" To: "'Dima Dorfman'" , "'Robert'" Cc: Subject: RE: Cron still exiting signal 11. Date: Sat, 14 Jul 2001 10:15:16 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal In-Reply-To: <20010714055851.693D93E2F@bazooka.unixfreak.org> Disposition-Notification-To: "Lanny Baron" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I don't think you get it. Cron is exiting upon reboot. There is a size difference between my last cvsup for 4.3-STABLE and one this week. But now I cannot even cvsup. The pod2man is messed up so bad, that even putting in the path in the /usr/src/secure/usr.bin/openssl/Makefile gets changed during the makebuildworld and consequently, 9 attempts at getting a cvsup to succeed, failed. --lanny -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of Dima Dorfman Sent: Saturday, July 14, 2001 1:59 AM To: Robert Cc: freebsd-stable@freebsd.org Subject: Re: Cron still exiting signal 11. Robert writes: > What is up with "cron" not working? > > I cvsup'd last night and its still br0ke. It works fine unless you don't specify a username in /etc/crontab. It's a bug that it crashes instead of civilly reporting the error, but it has never and will never do what you want until you fix the syntax error in your crontab. > > -Robert > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message