summary refs log tree commit diff stats
path: root/stubs/iothread-lock-block.c
diff options
context:
space:
mode:
authorHanna Reitz <hreitz@redhat.com>2022-03-03 17:48:13 +0100
committerKevin Wolf <kwolf@redhat.com>2022-03-04 18:14:40 +0100
commit2525edd85fec53e23fda98974a15e3b3c8957596 (patch)
treed27ad4f3ee0f0d3a238f23bbfc2e2553d647abdc /stubs/iothread-lock-block.c
parent79d51d7317c204dedd220793950a50f46a4e5bd9 (diff)
downloadfocaccia-qemu-2525edd85fec53e23fda98974a15e3b3c8957596.tar.gz
focaccia-qemu-2525edd85fec53e23fda98974a15e3b3c8957596.zip
qsd: Add --daemonize
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>
Message-Id: <20220303164814.284974-4-hreitz@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'stubs/iothread-lock-block.c')
0 files changed, 0 insertions, 0 deletions