From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 0.14.0-rc2 is available
Date: Wed, 16 Feb 2011 18:16:12 +0100 [thread overview]
Message-ID: <4D5C065C.3050309@redhat.com> (raw)
In-Reply-To: <4D5C0253.5050205@codemonkey.ws>
Hi,
>> Indeed. It isn't a pidfile, it is a shared memory segment where spice
>> stores statistics. spice registers a cleanup handler via atexit()
>> which removes this
>
> fork() with an inherited pipe and then waiting for EOF on the pipe() is
> a bit more robust of a mechanism to handle this.
Feels a bit like overkill in that case though. The extra process
doesn't come for free. We are talking about a shared memory segment
with a single page only. It is leaked only on crashes. It can
trivially be cleaned up manually if needed, just rm the file.
cheers,
Gerd
next prev parent reply other threads:[~2011-02-16 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 21:48 [Qemu-devel] [ANNOUNCE] QEMU 0.14.0-rc2 is available Anthony Liguori
2011-02-16 16:28 ` Rick Vernam
2011-02-16 16:37 ` Anthony Liguori
2011-02-16 16:52 ` Gerd Hoffmann
2011-02-16 16:58 ` Anthony Liguori
2011-02-16 17:16 ` Gerd Hoffmann [this message]
2011-02-16 17:18 ` Gerd Hoffmann
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=4D5C065C.3050309@redhat.com \
--to=kraxel@redhat.com \
--cc=anthony@codemonkey.ws \
--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).