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

Re: [BUG?] gc and impatience

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 3, 2013, 04:44 UTC
Message-ID
<CAPc5daXi_ZG6GcK6pWafffyOY4MEZHUMkZxTxiRiU4BaFybqqg@mail.gmail.com>
In-Reply-To
<CACsJy8DRo9Akoydwn9-EPOSyJiPhqAf1=HncYjHvXZwS4S_d7A@mail.gmail.com>
On Fri, Aug 2, 2013 at 8:53 PM, Duy Nguyen <pclouds@gmail.com> wrote:
> Good point. I think that is because gc does not check if gc is already
> running. Adding such a check should not be too hard. I think gc could
> save its pid in $GIT_DIR/auto-gc.pid. The next auto-gc checks this, if
> the pid is valid, skip auto-gc.

Defining "valid" is a tricky business, though, as pid can and will wrap around, and the directory could be shared on multiple machines. A pid written by a process on one machine has no relation to any pid on another machine.

Previous: Duy NguyenNext: Duy Nguyen
Message 3 of 7 in “[BUG?] gc and impatience”
  1. Ramkumar RamachandraAug 3, 2013
  2. Duy NguyenAug 3, 2013
  3. Junio C HamanoAug 3, 2013
  4. Duy NguyenAug 3, 2013
  5. Junio C HamanoAug 5, 2013
  6. Ramkumar RamachandraAug 5, 2013
  7. Ramkumar RamachandraAug 6, 2013

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.