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 sales@march-hare.com.
Hi Glen, I tried postcommit, but it's not what I want. And still have this problem. Postcommit is between commitfile and remove the write file lock. I also traced the source code and it LOOKS fine to me. :( My work around is prepare a batch file and run it manually :( Regards, James Sa -----Original Message----- From: Glen Starrett [mailto:grstarrett at cox.net] Sent: Friday, October 17, 2003 12:00 AM To: James Sa (RD-TW); cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: RE: [cvsnt] loginfo lock problem > > It works well on my debian box for 1 year. But I setup an > CVSNT server on > windows 2003 recently. I rewrite the loginfo to : > > ^myprog ( cd c:\inetpub\lastest & cvs -q update -d ) > > The CVS server will return following error message. > > cvs update: [15:32:52] waiting for james on my.url.com's lock in > c:/cvs/vision/src > > But if I do this update manually (without using loginfo), > everything works > fine. :( I believe you should be using postcommit instead of loginfo, but I don't have any direct knowledge on what fires when or how it works behind the scenes. I think postcommit will solve the problem. There is some comments in the files themselves and in the cvsnt wiki documentation, perhaps that can help answer your other questions. Hope this helps. Regards, Glen Starrett