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

Re: lockfiles & fork()

From
FWFlorian Weimer <fw@deneb.enyo.de>
Date
Oct 28, 2006, 13:30 UTC
Message-ID
<87fyd8ftzg.fsf@mid.deneb.enyo.de>
In-Reply-To
<Pine.LNX.4.63.0610280319250.26682@wbgn013.biozentrum.uni-wuerzburg.de>
* Johannes Schindelin:
Show 5 quoted lines
> when you setup a lockfile, and then fork(), you could easily end up with 
> atexit() kicking in to remove the lockfile, before the main process has a 
> chance to commit. (Yes, I need to hold the lock long before the fork()).
>
> Any ideas how to solve the problem?
I think you should call _exit in the child instead of exit.
Previous: Linus Torvalds
Message 4 of 4 in “lockfiles & fork()”
  1. Johannes SchindelinOct 28, 2006
  2. Junio C HamanoOct 28, 2006
  3. Linus TorvaldsOct 28, 2006
  4. Florian WeimerOct 28, 2006

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.