[cvsnt] 2.0.20 - brocken lock server port

Robert Sauer dave.loper at web.de
Mon Jan 12 10:41:09 GMT 2004


Hi Toni,

I have my lock server not running on the default port, but on 4804.
Both 2.0.19 and 2.0.20 do not honor the new "LockServer" registry
property, but still read the old one "LockServerPort".
Recreating this property by hand or using the 2.0.14 cvsnt.cpl
fixes this ad hoc.

Thanks,
Robert



More information about the cvsnt mailing list