From: David Barrett <dbarrett@quinthar.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Setting new user:group with -daemonize?
Date: Tue, 15 Jul 2008 19:14:28 -0700 [thread overview]
Message-ID: <487D5984.7080103@quinthar.com> (raw)
In-Reply-To: <487D515A.90903@codemonkey.ws>
Anthony Liguori wrote:
> David Barrett wrote:
>>
>> I'd update the -daemonize syntax as follows:
>>
>> -daemonize [user[:group]]
>>
>> Is there any interest in such a patch?
>
> If you introduced two new options to specify the user and the group.
Ok, so you're saying you prefer two new options:
-user <user>
-group <group>
> Also, I would be interested in a chroot option too :-)
Adding the following also seems easy enough:
-chroot <path>
If I build it, any estimate of how long it'd take to make it into the
next mainline release?
>> PS: Why does it fork twice?
>
> It makes sure QEMU is an orphan process (it's parent is pid 1). It's a
> pretty typical thing to do when daemonizing.
Ah, very clever.
-david
next prev parent reply other threads:[~2008-07-16 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 23:09 [Qemu-devel] Setting new user:group with -daemonize? David Barrett
2008-07-16 1:39 ` Anthony Liguori
2008-07-16 2:14 ` David Barrett [this message]
2008-07-18 17:00 ` Ian Jackson
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=487D5984.7080103@quinthar.com \
--to=dbarrett@quinthar.com \
--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.