Are you using WinCVS? If so, ours was crashing too because the username
that we were using wasn't listed in the CVSROOT/passwd file (and we are
allowing the system to fall-back to system authentication).
BTW: If nobody else is using cvs, then you can remove the lock files.
-----Original Message-----
From: Dennis Jones [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 31, 2001 9:56 AM
To: CVS Mailing List
Subject: Re: fatal signal and .rfl locks
Well, I couldn't wait for an answer, so I deleted the files. I still got
the fatal signal and segmentation faults, so I figured there was something
going on in the filesystem. So, I rebooted the server and was going to run
fsck, but all is well after the reboot. Very strange.
- Dennis
----- Original Message -----
From: "Dennis Jones" <[EMAIL PROTECTED]>
To: "CVS Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, May 31, 2001 8:30 AM
Subject: fatal signal and .rfl locks
> When I do an update, I get the message,
>
> "Terminated with fatal signal 11"
>
> It seems to be happening in the same place everytime, so I went to the
> directory on the CVS server where it stops, did an "ls" and found some
> #cvs.rfl.... files there. If I try to list those files (using ls -la) to
> get their time stamp, I get a segmentation fault.
>
> Nobody is using CVS right now, is it safe to delete those files? Should I
> be concerned about a possible disk fault or disk errors?
>
> - Dennis
>
>
> _______________________________________________
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
