waiting for lock message on cvs
Hi I did a very stupid mistake while trying to commit something ona new machine. when i tried to commit a file , I did not have a default editor set up. so it opened a vim editor to log in my messages. Since I am not familiar with vim, I killed th cvs commit job (using kill -9 pid). Then when I set the editor to be emacs it and tried to commit the same file I get the error message cvs commit: cvs commit: [11:28:28] waiting for melroy's lock [11:28:28] I looked at the past archives and cvs manual to look for this solution and it appears that this message occurs when two people simulatenously try to commit something. anyhow can someone suggest a simple solution? Is there alock file which I should look for and delete? Thanks a lot Melroy ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: waiting for lock message on cvs
<#part sign=pgp [EMAIL PROTECTED]> Melroy <[EMAIL PROTECTED]> writes: > I did a very stupid mistake while trying to > commit something ona new machine. > when i tried to commit a file, I did not have a > default editor set up. Clearly, the default editor you had was vim. However, you didn't have a personal EDITOR or CVSEDITOR setup. > so it opened a vim editor to log in my messages. > Since I am not familiar with vim, I killed th > cvs commit job (using kill -9 pid). Then when I > set the editor to be emacs it and tried to > commit the same file I get the error message > cvs commit: cvs commit: [11:28:28] waiting for melroy's lock > [11:28:28] > I looked at the past archives and cvs manual to > look for this solution and it appears that this > message occurs when two people simulatenously > try to commit something. anyhow can someone > suggest a simple solution? You will need to go to the repository and remove the cvs lock file for the directory. If you used LockDir= in the CVSROOT/config the lock will be found under the tree. Otherwise, it will be in your $CVSROOT/ directory. > Is there alock file which I should look for and > delete? Yes. Read https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_2.html#SEC17 it should help you identify what needs to be fixed. -- Mark ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: waiting for lock message on cvs
The other thing you should do is avoid using kill -9 as your first resort to get rid of something you don't want. It's a "kill with extreme prejudice" command that blasts the process slot without giving the application a chance to clean up after itself. Try using ctrl-C, then just plain kill, then maybe kill -1 before going for the throat. Had you done this instead, CVS' signal handlers would have cleared the locks for you. Melroy <[EMAIL PROTECTED]> writes: > I did a very stupid mistake while trying to > commit something ona new machine. > Since I am not familiar with vim, I killed th > cvs commit job (using kill -9 pid). Then when I > set the editor to be emacs it and tried to > commit the same file I get the error message > cvs commit: cvs commit: [11:28:28] waiting for melroy's lock > [11:28:28] ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
AW: waiting for lock message on cvs
> -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Im > Auftrag von Paul Sander > Gesendet: dinsdag 28 september 2004 16:27 > Betreff: Re: waiting for lock message on cvs > > The other thing you should do is avoid using kill -9 as your > first resort to get rid of something you don't want. It's a Especially with vim and cvs... Poor tools ;) You might want to read some manuals as well as to how to get out of vim, once this scary editor pops up... Guus --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004 ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: waiting for lock message on cvs
[EMAIL PROTECTED] wrote: > The other thing you should do is avoid using kill -9 as your > first resort > to get rid of something you don't want. ... > Try using ctrl-C, then > just plain kill, then maybe kill -1 before going for the > throat... Heck, even a ctrl-C is (ahem) overkill. If you exit the editor without saving, CVS will complain about an empty log message, and ask if you want to abort, continue, go back into the editor, or use the (empty) message anyway. 'Least that's how my installation works - it's not a configurable option, is it? -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
