Dimitrie O. Paun writes:
>
> Hmm, I figured that would be the case, but I can't seem to figure out
> what is the problem. But, just to put my mind at ease, this is not normal,
> right? Can an error on the client side screw up the server? That is,
> what happens if I kill (or crash) the client at random points? Will the
> server
> behave properly and clean up after itself?
It should.
> > You're not running with PreservePermissions enabled, are you?
>
> No. Here is my CVSROOT/config file:
Have you ever run with PreservePermissions?
> > Have you had complaints from users?
>
> Well, quite a few, as you can imagine -- we get these locks laying around
> all the time, so a lot of people are running into them.
I meant complaints about CVS crashing, not the leftover locks!
> Apart from this
> problem, the cvs server dies on a few files with this error:
>
> fileattr.c:52: fileattr_stardir: Assertion 'unrecog_head = ((void *) 0)'
> failed
That would explain the problem -- an assertion failure is a serious
error that causes the server to quit without cleaning up. I think I see
what's causing this particular problem and I'm testing a fix.
(Although, as Steve Cameron has noted, the CVS source repository is
currently off-line, so I can't check it in.)
-Larry Jones
When you're as far ahead of the class as I am, it doesn't take much time.
-- Calvin
