From: fork0@t-online.de (Alex Riesen)
To: Marco Costalba <mcostalba@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Easy shell question: how to make a script killing all his childs when killed?
Date: Sat, 9 Dec 2006 22:39:37 +0100 [thread overview]
Message-ID: <20061209213937.GB12373@steel.home> (raw)
In-Reply-To: <e5bfff550612090951l43a83a00o7ea2e244ca562c77@mail.gmail.com>
Marco Costalba, Sat, Dec 09, 2006 18:51:57 +0100:
> >> P.S: I have no way to exec the script in fancy ways, I can just start
> >> it and get is PID.
> >
> >Which is "fancy" enough. What do you mean "start"? Starting a new
> >process usually and notably involves forking and execing (even if the
> >first thing to exec will be your shell).
>
> By 'start' I mean it is done inside Qt QProcess class back box ;-)
>
> Anyway I have written an homegrown 'wanna be hacker' launching script:
>
> git rev-list --header --boundary --parents --topo-order HEAD >
> /tmp/qgit_136224752.txt &
> echo $!
> wait
>
> With this I can get the pid of git-rev-list from my QProcess interface
> so to be able to kill it when needed with another command ('kill'
> BTW).
Why do you need to save it in temporary file at all? Why don't you
read the output like gitk does? You can take a look at popen(3). It's
known to be portable among operating systems and libc's. Or, BTW, why
don't you just read qprocess.h, use processIdentifier()/pid(),
read*()-methods and the like? (though, looking at the QProcess in
next prev parent reply other threads:[~2006-12-09 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 15:16 Easy shell question: how to make a script killing all his childs when killed? Marco Costalba
2006-12-09 17:37 ` Alex Riesen
2006-12-09 17:51 ` Marco Costalba
2006-12-09 21:39 ` Alex Riesen [this message]
2006-12-09 23:06 ` Marco Costalba
2006-12-10 14:25 ` Alex Riesen
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=20061209213937.GB12373@steel.home \
--to=fork0@t-online.de \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.com \
--cc=raa.lkml@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).