From: Tim <tim-qemu@sentinelchicken.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Trivial (but useful) patch to save qemu pid to file
Date: Wed, 8 Dec 2004 21:11:21 -0500 [thread overview]
Message-ID: <20041209021121.GA2064@sentinelchicken.org> (raw)
In-Reply-To: <41B779A0.5050601@bellard.org>
> I can include this patch if it helps some people as it seems rather non
> intrusive.
I personally rather manage my daemons with something like daemontools or
runit:
http://cr.yp.to/daemontools.html
http://smarden.org/runit/
But like you say, it is pretty non-intrusive as it is off by default.
For some it will probably help out.
tim
next prev parent reply other threads:[~2004-12-09 2:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 9:38 [Qemu-devel] Syscall 269 James Pellow
2004-11-18 13:03 ` Paul Brook
2004-11-18 18:24 ` James Pellow
2004-12-04 0:05 ` James Pellow
2004-12-04 15:09 ` Paul Brook
2004-12-06 1:16 ` James Pellow
2004-12-06 1:26 ` Paul Brook
2004-12-06 2:58 ` James Pellow
2004-12-08 0:07 ` [Qemu-devel] Trivial (but useful) patch to save qemu pid to file Nile Geisinger
2004-12-08 18:12 ` Felipe Sanchez
2004-12-08 22:01 ` Fabrice Bellard
2004-12-09 2:11 ` Tim [this message]
2004-12-13 13:20 ` Nile Geisinger
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=20041209021121.GA2064@sentinelchicken.org \
--to=tim-qemu@sentinelchicken.org \
--cc=qemu-devel@nongnu.org \
/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).