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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Dima Dorfman
Sent: Saturday, July 14, 2001 1:59 AM
To: Robert
Cc: [EMAIL PROTECTED]
Subject: Re: Cron still exiting signal 11.
Robert <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
