From: Florian Weimer <fw@deneb•enyo.de>
To: git@vger•kernel.org
Subject: Re: lockfiles & fork()
Date: Sat, 28 Oct 2006 15:30:27 +0200 [thread overview]
Message-ID: <87fyd8ftzg.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0610280319250.26682@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Sat, 28 Oct 2006 03:21:38 +0200 (CEST)")
* Johannes Schindelin:
> 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.
prev parent reply other threads:[~2006-10-28 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 1:21 lockfiles & fork() Johannes Schindelin
2006-10-28 1:41 ` Junio C Hamano
2006-10-28 1:52 ` Linus Torvalds
2006-10-28 13:30 ` Florian Weimer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fyd8ftzg.fsf@mid.deneb.enyo.de \
--to=fw@deneb$(echo .)enyo.de \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox