[cvsnt] Re: cvslock application error

[Tony Hoyle]

Murphy, John wrote:

> 
> [ffffffff] The specified network name is no longer available.

Sounds like your network is dropping out periodically.  This may explain 
the hanging too as cvs really relies on the network being up.

> A couple of other things to note.  The repository is quite busy, with
> about 40 developers using it, but the bulk of the work the server does
> is serving requests that originate from cruise control which we use to
> run continuous integration builds.  I upgraded the server this weekend
> and this problem has happened 3 times in the last two days.

Don't run continuous updates like that - Run an update in postcommit and 
trigger a build from there.  You're just running your server into the 
ground for no reason otherwise... On average an update should take maybe 
a few seconds and use little memory... cruise control does a full 
checkout sometimes several times a minute!

Make a script that keeps an updated checked out repository, and after 
the update fire a background task to copy this to a staging area for 
building (possibly periodically, depending on how often this happens).

> Have you seen this problem before?  Any ideas about how to rectify this
> situation would be greatly appreciated.

cvslock doesn't really do anything, other than store information in it. 
   There was one other person who reported something but he was adding 
something like 10000 files simultaneously and I suspect simply ran out 
of memory.

Tony