RE: [Non-DoD Source] Re: CVS lock issue
"Glasgow, Steven R CIV USARMY TRAC (US)" <[email protected]> Thu, 15 Feb 2018 20:20:38 +0000
| Newsgroups | gmane.comp.version-control.cvs.general |
|---|---|
| Message-ID | <6132691E064DAC49B214555A63470274D2606CFA@UTINHUAE1.easf.csd.disa.mil> |
Could it be possible that two developers tried to tag the file at the same = time? I thought CVS handled that situation. Could it be possible that one developer created the lock and a second one w= as not able to do that (file exists). I thought the first developer would = have created the #cvs.lock directory making the second developer wait to e= ven access the <path> directory. Thanks, Steve -----Original Message----- From: Glasgow, Steven R CIV USARMY TRAC (US)=20 Sent: Thursday, February 15, 2018 2:15 PM To: [email protected] Subject: RE: [Non-DoD Source] Re: CVS lock issue The file is no longer there. This error occurred on Feb 01 according to a = log file we maintain. We just noticed that the entire module did not get t= agged. Could it be that a subsequent process to that area of the module al= ready removed the lock sometime between then and now? I wish the file was still there, but it's not. Why would a lock file not get deleted? Thanks, Steve -----Original Message----- From: info-cvs [mailto:info-cvs-bounces+steven.r.glasgow.civ=3Dmail.mil@non= gnu.org] On Behalf Of Spiro Trikaliotis Sent: Thursday, February 15, 2018 2:00 PM To: [email protected] Subject: [Non-DoD Source] Re: CVS lock issue All active links contained in this email were disabled. Please verify the = identity of the sender, and confirm the authenticity of all links contained= within the message prior to copying and pasting the address to a Web brows= er. =20 ---- Hello, * On Thu, Feb 15, 2018 at 07:42:30PM +0000 Glasgow, Steven R CIV USARMY TRA= C (US) wrote: > cvs [tag aborted]: could not open lock file `<path>/,<filen+2>.cc,`:=20 > File exists >=20 > How is it possible that the ,<filen+2>.cc, lock already existed? Have a look into the file, especially the date and time. Is it (very) old? There might have been an older operation that did not correctly finish, and= the lock file has been left over. In this case, the lock file would be rat= her old. I would consider removing it by hand, then. If it is not old, then something else is going on, and I would refrain from= removing it. HTH, Spiro. -- Spiro R. Trikaliotis Caution-http://www.trikaliotis.net/