2012-05-21 11:05 AEST by Arthur Barrett - On startup the event log shows: Failed to bind listening socket: The operation completed successfully.

2012-05-21 11:13 AEST by Arthur Barrett - Created an attachment (id=2398)
patch - debugging

This doesn't seem to occur all the time, and doesn't appear to affect
reliability (probably because the service is configured to auto-restart?)/

add some extra diagnostics to assist in debug...


Checking in cvsapi/win32/SocketIO.cpp;
/cvs/cvsnt/cvsapi/win32/SocketIO.cpp,v	<--  SocketIO.cpp
new revision: 1.1.2.14.4.9.2.24; previous revision: 1.1.2.14.4.9.2.23
done
Checking in lockservice/lockservice.cpp;
/cvs/cvsnt/lockservice/lockservice.cpp,v  <--  lockservice.cpp
new revision: 1.5.2.25.4.4.2.3; previous revision: 1.5.2.25.4.4.2.2
done
Checking in lockservice/server.cpp;
/cvs/cvsnt/lockservice/server.cpp,v  <--  server.cpp
new revision: 1.6.2.48.6.13.2.1; previous revision: 1.6.2.48.6.13
done
Checking in simcvs/res/simcpl.manifest;
/cvs/cvsnt/simcvs/res/simcpl.manifest,v  <--  simcpl.manifest
new revision: 1.1.4.1.2.2; previous revision: 1.1.4.1.2.1
done

2012-05-21 15:57 AEST by Arthur Barrett - on windows 7 x64 this happens when you try and use :local: to initialize a new 
repository, eg:

cvs.exe -d C:\PROGRA~3\MARCHH~1\nyrepo init -n -a /myrepo
cvs init: Repository C:\PROGRA~3\MARCHH~1\nyrepo initialised


It seems like cvsnt.exe is attempting to start a cvslock.exe process, which is 
not needed because there is already one running.

So what to do:
- stop cvsnt.exe trying to start cvslock unnecessarily
- have cvslock.exe detect if there is already a service running / port 2402
- do not display event log messages if not running as a service


Regardless, this is low priority because it all works OK anyway...