[cvsnt] Cvslockd won't run on
dsomers at omz13.com
Tue Dec 12 21:03:30 GMT 2006
Cryer, Phil C. (STL) - cont wrote:
> cvs at esi1p83d:/usr/local/bin>./cvslockd -d
> Could not open /etc/cvsnt/PServer
I guess you are using linux.
What version of cvsnt are you using?
> Initialising socket...
> Starting lock server on port 2402/tcp...
> Socket bind failed: errno 126 on socket 3 (AF 26) - closing socket
> Socket bind failed: errno 125 on socket 4 (AF 2) - closing socket
> Couldn't bind listening socket... Address already in use
> cvs at esi1p83d:/usr/local/bin>
> So I restarted at cvslockd -p 2403 -- is there any issue with not
> running it on the default?
Use netstat to see who has bound to the port (i.e. netstat -ap | grep
2402)... I've had the occasional instance of cvslockd crashing/locking and
keeping the port bound... is that's the case, pkill is your friend.
> Also, do I have to run the cvslockd server?
> From the docs I thought it was needed only if we wanted a read-only
> but I'm going to be setting all permissions via ACL; some
> will be read only - some read write...do I need cvslockd to be running?
> And if so, do I need to tell cvsnt where to find cvslockd since it's on
> 03 instead of 02?
Yes. (But its probably better to find why 2402 is in use, rather than
working around the problem.)
More information about the cvsnt