From: Markus Armbruster <armbru@redhat.com>
To: Hanna Reitz <hreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH 1/3] qsd: Add pre-init argument parsing pass
Date: Wed, 19 Jan 2022 13:58:24 +0100 [thread overview]
Message-ID: <87zgnrubkf.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20211222114153.67721-2-hreitz@redhat.com> (Hanna Reitz's message of "Wed, 22 Dec 2021 12:41:51 +0100")
Hanna Reitz <hreitz@redhat.com> writes:
> We want to add a --daemonize argument to QSD's command line.
Why?
> This will
> require forking the process before we do any complex initialization
> steps, like setting up the block layer or QMP. Therefore, we must scan
> the command line for it long before our current process_options() call.
Can you explain in a bit more detail why early forking is required?
I have a strong dislike for parsing more than once...
> Instead of adding custom new code to do so, just reuse process_options()
> and give it a @pre_init_pass argument to distinguish the two passes. I
> believe there are some other switches but --daemonize that deserve
> parsing in the first pass:
>
> - --help and --version are supposed to only print some text and then
> immediately exit (so any initialization we do would be for naught).
> This changes behavior, because now "--blockdev inv-drv --help" will
> print a help text instead of complaining about the --blockdev
> argument.
> Note that this is similar in behavior to other tools, though: "--help"
> is generally immediately acted upon when finding it in the argument
> list, potentially before other arguments (even ones before it) are
> acted on. For example, "ls /does-not-exist --help" prints a help text
> and does not complain about ENOENT.
>
> - --pidfile does not need initialization, and is already exempted from
> the sequential order that process_options() claims to strictly follow
> (the PID file is only created after all arguments are processed, not
> at the time the --pidfile argument appears), so it makes sense to
> include it in the same category as --daemonize.
>
> - Invalid arguments should always be reported as soon as possible. (The
> same caveat with --help applies: That means that "--blockdev inv-drv
> --inv-arg" will now complain about --inv-arg, not inv-drv.)
>
> Note that we could decide to check only for --daemonize in the first
> pass, and defer --help, --version, and checking for invalid arguments to
> the second one, thus largely keeping our current behavior. However,
> this would break "--help --daemonize": The child would print the help
> text to stdout, which is redirected to /dev/null, and so the text would
> disappear. We would need to have the text be printed to stderr instead,
> and this would then make the parent process exit with EXIT_FAILURE,
> which is probably not what we want for --help.
>
> This patch does make some references to --daemonize without having
> implemented it yet, but that will happen in the next patch.
>
> Signed-off-by: Hanna Reitz <hreitz@redhat.com>
next prev parent reply other threads:[~2022-01-19 13:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 11:41 [PATCH 0/3] qsd: Add --daemonize; and add job quit tests Hanna Reitz
2021-12-22 11:41 ` [PATCH 1/3] qsd: Add pre-init argument parsing pass Hanna Reitz
2021-12-30 16:00 ` Vladimir Sementsov-Ogievskiy
2022-01-03 16:14 ` Hanna Reitz
2022-01-19 12:58 ` Markus Armbruster [this message]
2022-01-19 13:44 ` Hanna Reitz
2022-01-19 17:21 ` Kevin Wolf
2022-01-20 16:00 ` Markus Armbruster
2022-01-20 16:31 ` Hanna Reitz
2022-01-21 6:10 ` Markus Armbruster
2022-01-21 8:43 ` Hanna Reitz
2022-01-21 10:27 ` Markus Armbruster
2022-01-21 11:16 ` Hanna Reitz
2022-01-21 14:26 ` Markus Armbruster
2022-01-24 8:20 ` Hanna Reitz
2022-01-24 9:23 ` Markus Armbruster
2022-01-24 9:34 ` Hanna Reitz
2021-12-22 11:41 ` [PATCH 2/3] qsd: Add --daemonize Hanna Reitz
2021-12-30 16:12 ` Vladimir Sementsov-Ogievskiy
2022-01-03 17:15 ` Hanna Reitz
2021-12-22 11:41 ` [PATCH 3/3] iotests/185: Add post-READY quit tests Hanna Reitz
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=87zgnrubkf.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@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.