From: Eric Blake <eblake@redhat.com>
To: Hanna Reitz <hreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH v2 3/4] qsd: Add --daemonize
Date: Thu, 3 Mar 2022 16:31:30 -0600 [thread overview]
Message-ID: <20220303223130.vr2d7qi2lfh5pg26@redhat.com> (raw)
In-Reply-To: <20220303164814.284974-4-hreitz@redhat.com>
On Thu, Mar 03, 2022 at 05:48:13PM +0100, Hanna Reitz wrote:
> To implement this, we reuse the existing daemonizing functions from the
> system emulator, which mainly do the following:
> - Fork off a child process, and set up a pipe between parent and child
> - The parent process waits until the child sends a status byte over the
> pipe (0 means that the child was set up successfully; anything else
> (including errors or EOF) means that the child was not set up
> successfully), and then exits with an appropriate exit status
> - The child process enters a new session (forking off again), changes
> the umask, and will ignore terminal signals from then on
> - Once set-up is complete, the child will chdir to /, redirect all
> standard I/O streams to /dev/null, and tell the parent that set-up has
> been completed successfully
>
> In contrast to qemu-nbd's --fork implementation, during the set up
> phase, error messages are not piped through the parent process.
> qemu-nbd mainly does this to detect errors, though (while os_daemonize()
> has the child explicitly signal success after set up); because we do not
> redirect stderr after forking, error messages continue to appear on
> whatever the parent's stderr was (until set up is complete).
>
> Signed-off-by: Hanna Reitz <hreitz@redhat.com>
> ---
> docs/tools/qemu-storage-daemon.rst | 7 +++++++
> storage-daemon/qemu-storage-daemon.c | 15 +++++++++++++++
> 2 files changed, 22 insertions(+)
>
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2022-03-03 22:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 16:48 [PATCH v2 0/4] qsd: Add --daemonize; and add job quit tests Hanna Reitz
2022-03-03 16:48 ` [PATCH v2 1/4] os-posix: Add os_set_daemonize() Hanna Reitz
2022-03-03 20:22 ` Eric Blake
2022-03-04 9:19 ` Daniel P. Berrangé
2022-03-04 10:20 ` Kevin Wolf
2022-03-04 11:58 ` Daniel P. Berrangé
2022-03-03 16:48 ` [PATCH v2 2/4] qsd: Add pre-init argument parsing pass Hanna Reitz
2022-03-03 22:27 ` Eric Blake
2022-03-03 16:48 ` [PATCH v2 3/4] qsd: Add --daemonize Hanna Reitz
2022-03-03 22:31 ` Eric Blake [this message]
2022-03-04 9:27 ` Kevin Wolf
2022-03-03 16:48 ` [PATCH v2 4/4] iotests/185: Add post-READY quit tests Hanna Reitz
2022-03-03 22:36 ` Eric Blake
2022-03-04 10:47 ` [PATCH v2 0/4] qsd: Add --daemonize; and add job " Kevin Wolf
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=20220303223130.vr2d7qi2lfh5pg26@redhat.com \
--to=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.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 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.