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.
Ah, yes, I'm guessing you hit the old -kx. You can verify it by doing a "cvs stat" on one of the files and seeing if it has the expansion option x. When you commit files with Tortoise for example it marks all your binary files for exclusive write. It expects you to use "cvs edit". So you have a couple of choices. You can modify your workflow to use the "cvs edit" command before modifying the file, or you can "cvs update -k-x" and then "cvs commit" to remove the exclusive write. If that's not your problem, then it's likely "cvs watch off" to fix it. Unlike "cvs watch add" which sends email to a specific user, "cvs watch on" just seems to make all the files read-only (again expecting "cvs edit"). I'm not exactly sure of the purpose for this feature, but I know that turning it off doesn't remove watches but does make the files writable again. HTH chuck Gordon Boast wrote: > Thanks Peter. > > Investigation revealed that the something else was another copy of > cvslock -- sure where it came from. Killed it off and it does not come > back. > > Was able to check-out all projects -- which has raised yet another > issue: some files (I think binary files, but can't be sure) have > checked out as read-only. > > Does anyone know why this is? Is there a way to get ALL files to > check-out read/write? > > Thanks, > > Gordon > > -----Original Message----- > From: Peter Crowther [mailto:Peter.Crowther at melandra.com] > Sent: Monday, July 07, 2008 4:53 PM > To: 'gordon.boast at ieee.org'; cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Subject: RE: [cvsnt] Need help installing cvsnt..... > > >> From: Gordon Boast >> There remains one issue I have not seem before: the lock server > won't >> start -- it posts the following error message: Failed to bind >> listening socket: Only one usage of each socket address >> (protocol/network address/port) is normally permitted. >> >> Lock server is set: localhost and port 2402 > > Something else is using port 2402. Depending on your operating > system, there are different ways of finding out what it is! > > - Peter > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 3248 (20080707) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > >