Re: [Savannah-hackers] Problem with stale lock

[Sylvain Beucler]

The cvs processes you killed still had their Savannah counterpart  
alive, and I suppose that's why they kept trying to lock.
Now those are killed, they nicely unlocked the repository.

I am amazed such processes can wait for about 4h30 without dying...
Anybody has an explanation for this?

# date
Sat Feb 28 14:10:30 EST 2004

# ps aux | grep ^dak
dak      21113  0.0  0.0   996  368 ? S    09:40   0:00 /bin/cvs server
dak      21121 94.4  0.0  1416  768 ? R    09:40 250:18 /bin/cvs server
dak      22381  0.0  0.0  1000  376 ? S    09:49   0:00 /bin/cvs server
dak      22400 72.4  0.0  1424  784 ? R    09:49 185:44 /bin/cvs server
dak       6581  0.0  0.0   992  364 ? S    11:14   0:00 /bin/cvs server
dak       6691 92.6  0.0  1412  764 ? R    11:14 158:50 /bin/cvs server
dak      32604  0.0  0.0  5860 1688 ? S    13:38   0:00 /usr/sbin/sshd
dak      32608  0.0  0.0  1000  372 ? S    13:38   0:00 /bin/cvs server
dak      32721 84.3  0.0  1420  772 ? R    13:38  22:54 /bin/cvs server

--
Sylvain


On 2004.02.28 19:48, David Kastrup wrote:
> Sylvain Beucler <address@hidden> writes:
>
> > I'm back and I removed the lock again.
> >
> > I wonder why locks appears. The systems says you created them.
>
> Sigh.  The first time this happened when I tried to check in
> /cvsroot/auctex/auctex/latex.el, and it hangs in the checkin right
> now.  Whenever I try to check in that file, it hangs.  I have no clue
> why this would be: there had been a branch on that file until
> recently, but I am trying to check into the trunk.  I was able to
> check out the head version,do my changes on it, but checking in hangs
> CVS.
>
> I'll just let the process linger for now until you tell me what to  
> do.