Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Never mind, got it to work. I was putting a : before the port number instead of a space :) "Khaled Agrama" <kagrama at hotmail.com> wrote in message news:al5rff$gmk$1 at sisko.nothing-on.tv... > I installed this build but can't get telnet to work. Is there anything > special I need to do? > > Khaled. > > "Tony Hoyle" <tmh at nothing-on.tv> wrote in message > news:3d6f8562.1299907171 at news.cvsnt.org... > > cvsnt 184.108.40.206 57h > > > > Mostly this release is so I can push the lock server into production > > here (as we need it). Some bug fixes. Made the Unix version execute > > commands via the shell like it used to. > > > > The Lock server is a separate service/daemon that keeps track of the > > current locks on the repository. To use it set a line if > > CVSROOT/config that says 'LockServer=<server>[:port]' (normally you'd > > run the server on the same machine as the cvsnt server so > > 'LockServer=localhost' will do fine). Remove any LockDir lines. > > > > It defaults to port 2402, which shouldn't clash with anything (you can > > change it with the control panel). It's designed to be firewalled (you > > wouldn't normally access it across the internet) and there's no > > security at the moment - I'll add that later. > > > > You can monitor what the server is doing by telnetting into it and > > typing 'monitor'. The output is designed to be parsed by some > > (future) software but can be quite interesting to watch on a busy > > server. > > > > In theory it's impossible to get dangling locks - the locks are all > > automatically removed if the client exits even if it crashes horribly. > > > > At some point I'll document the protocol but it's extremely simple > > (it's actually documented in comments in the source at the moment). > > > > Tony > > > >