git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git .lock file error

From
Nate Parsons <parsons.nate@gmail.com>
Date
Oct 1, 2010, 00:57 UTC
Message-ID
<AANLkTi=eMt_OduJ8d=5mhhnt+q-Mpb8b1iimt_0bws3f@mail.gmail.com>
In-Reply-To
<AANLkTikV=f1ncAxQ1LWzntnOwiBKMfw_D8Mcuh+wCO3+@mail.gmail.com>
On Thu, Sep 30, 2010 at 7:45 PM, Erik Faye-Lund <kusmabite@gmail.com> wrote:
Show 8 quoted lines
> Are you running some anti-virus, or from a Dropbox-folder (or
> something similar)? If so, these applications tend to open files for a
> short while and then release the file handle. This can some times
> cause race conditions with other software, like Git.
>
> I haven't looked into this particular code-path for what kind of
> hazards might be, but this sounds very much like one such case to me.
>

Any of these things are possible. As much as I'd like to find the root cause of this problem, isn't making Git more robust a good thing in general? Finding every program that could conflict with Git and disabling/uninstalling it isn't really a good long term solution, I think.

Previous: Erik Faye-LundNext: Erik Faye-Lund
Message 9 of 10 in “git .lock file error”
  1. Nate ParsonsSep 13, 2010
  2. Nate ParsonsSep 20, 2010
  3. Nate ParsonsSep 30, 2010
  4. Ævar Arnfjörð BjarmasonSep 30, 2010
  5. Junio C HamanoSep 30, 2010
  6. Nate ParsonsSep 30, 2010
  7. Ævar Arnfjörð BjarmasonSep 30, 2010
  8. Erik Faye-LundSep 30, 2010
  9. Nate ParsonsOct 1, 2010
  10. Erik Faye-LundOct 1, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.