Date: Thu, 26 Feb 1998 15:55:01 -0500 (EST) From: Ted Buswell <tbuswell@mediaone.net> To: Doug White <dwhite@resnet.uoregon.edu> Cc: questions@FreeBSD.ORG Subject: Re: 2.2.5 cron and login.conf,/etc/group Message-ID: <199802262055.PAA13681@tbuswell.ne.mediaone.net> In-Reply-To: <Pine.BSF.3.96.980225204303.28338I-100000@gdi.uoregon.edu> References: <199802260133.UAA24837@tbuswell.ne.mediaone.net> <Pine.BSF.3.96.980225204303.28338I-100000@gdi.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Doug" == Doug White <dwhite@gdi.uoregon.edu> writes:
Doug> Odd it considers /etc/group corrupt AND that the path is in
Doug> caps. Can you identify? Perhaps it's another server logging
Doug> to yours?
/etc/group is fine, /etc/login.conf is fine (did a cap_mkdb too), and
the CAPS in the program name seem to come from the cron source..
I don't know what the problem is, but I can reproduce it easily on
this machine (HP Vectra/XU 6/200). My diagnosis is that cron is
allergic to Win95 :) Or maybe more accurately, this behavior seems to
be related to the use of fbsdboot.exe
To cause the problem:
1) boot Win95 into ms-dos mode.
2) boot freebsd using fbsdboot.exe
<cron problem happens>
3) /sbin/reboot
<don't bother using fbsdboot, just use "BootEasy">
<cron problem happens>
:goto 3
To get rid of the cron messages, all I have to do is do a hard reset
(/sbin/halt then hit the reset or power switch) and then boot FreeBSD
using the regular "BootEasy".
This is more than a little strange. I can reproduce it very easily,
so if anyone has any ideas, I'm willing to try them.
Thanks,
-Ted
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802262055.PAA13681>