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 everyone, I found an interesting problem in loginfo. I used to make a latest update to a certain directory. I did it by write script in loginfo. Like following, ^myprog ( cd /var/www/lastest; cvs -q update -d ) 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. :( Following is my observation, I found there're two cvs.exe process when loginfo try to call the script. I think first cvs.exe is taking care of the real commit action. After an successful commit, this cvs.exe reads and executes loginfo. Unfortunately, I called another cvs.exe in loginfo script. Therefore the second cvs.exe is waiting the first cvs.exe to unlock the write lock created by the commit action. Can someone tell me what happened behind the scene? Regards, James Sa