From: Paolo Bonzini <pbonzini@redhat.com>
To: Pierre Riteau <Pierre.Riteau@irisa.fr>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/4] qemu-nbd: do not start the block layer in the parent
Date: Fri, 28 Oct 2011 14:17:41 +0200 [thread overview]
Message-ID: <4EAA9D65.1080108@redhat.com> (raw)
In-Reply-To: <90216E5F-CF18-4A44-BBCF-0DFB68259296@irisa.fr>
On 10/28/2011 02:16 PM, Pierre Riteau wrote:
> Yes, it would be better if we could have error output on stderr. Now,
> "simple" errors such as a missing image file (or wrong path to the
> image) are reported to syslog instead. It could be the source of some
> headaches...
>
> Is there a way we could have the child send the error to the parent
> over a pipe and have the parent print it on stderr?
A way could be to change the fork() into a separate thread, so that you
can daemonize as soon as you accept the socket rather than having to do
it early.
Paolo
next prev parent reply other threads:[~2011-10-28 12:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 10:17 [Qemu-devel] [PATCH 0/4] fix qemu-nbd -c Paolo Bonzini
2011-10-28 10:17 ` [Qemu-devel] [PATCH 1/4] qemu-nbd: exit if the child exits before a socket connection is established Paolo Bonzini
2011-10-28 10:17 ` [Qemu-devel] [PATCH 2/4] qemu-nbd: include our own err/errx implementation Paolo Bonzini
2011-10-28 10:17 ` [Qemu-devel] [PATCH 3/4] qemu-nbd: report errors to syslog when daemonized Paolo Bonzini
2011-10-28 10:17 ` [Qemu-devel] [PATCH 4/4] qemu-nbd: do not start the block layer in the parent Paolo Bonzini
2011-10-28 11:56 ` Pierre Riteau
2011-10-28 11:57 ` Paolo Bonzini
2011-10-28 12:16 ` Pierre Riteau
2011-10-28 12:17 ` Paolo Bonzini [this message]
2011-11-04 9:46 ` Paolo Bonzini
2011-11-04 10:31 ` Kevin Wolf
2011-11-04 11:10 ` Paolo Bonzini
2011-11-04 11:22 ` Kevin Wolf
2011-11-04 11:25 ` Paolo Bonzini
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=4EAA9D65.1080108@redhat.com \
--to=pbonzini@redhat.com \
--cc=Pierre.Riteau@irisa.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.