From: Jonathan Nieder <jrnieder@gmail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: James Pickens <jepicken@gmail.com>, Git ML <git@vger.kernel.org>
Subject: Re: Background processes in post-receive hook
Date: Sun, 3 Apr 2011 00:06:19 -0500 [thread overview]
Message-ID: <20110403050619.GA32750@elie> (raw)
In-Reply-To: <BANLkTin4-fMhi_5H1oZ+gPB99stj5GRjVA@mail.gmail.com>
Sitaram Chamarty wrote:
> interestingly, the double fork trick doesn't work either...
>
> ( ( long-running-command & ) )
Hopefully closing the output pipe does the trick.
exec long-running-command >&- 2>&- &
Thanks for an interesting example.
Jonathan
prev parent reply other threads:[~2011-04-03 5:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 23:03 Background processes in post-receive hook James Pickens
2011-04-03 0:35 ` Junio C Hamano
2011-04-03 3:22 ` Sitaram Chamarty
2011-04-03 4:59 ` Joe Ratterman
2011-04-03 5:06 ` Jonathan Nieder [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=20110403050619.GA32750@elie \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jepicken@gmail.com \
--cc=sitaramc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).