From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: vsementsov@virtuozzo.com, qemu-block@nongnu.org
Subject: [PATCH] qemu-nbd: Document benefit of --pid-file
Date: Mon, 7 Oct 2019 14:48:40 -0500 [thread overview]
Message-ID: <20191007194840.29518-1-eblake@redhat.com> (raw)
One benefit of --pid-file is that it is easier to probe the file
system to see if a pid file has been created than it is to probe if a
socket is available for connection. Document that this is an
intentional feature.
Signed-off-by: Eric Blake <eblake@redhat.com>
---
qemu-nbd.texi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/qemu-nbd.texi b/qemu-nbd.texi
index 7f55657722bd..d495bbe8a0ed 100644
--- a/qemu-nbd.texi
+++ b/qemu-nbd.texi
@@ -118,7 +118,8 @@ in list mode.
@item --fork
Fork off the server process and exit the parent once the server is running.
@item --pid-file=PATH
-Store the server's process ID in the given file.
+Store the server's process ID in the given file. The pid file is not
+created until after the server socket is open.
@item --tls-authz=ID
Specify the ID of a qauthz object previously created with the
--object option. This will be used to authorize connecting users
--
2.21.0
next reply other threads:[~2019-10-07 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 19:48 Eric Blake [this message]
2019-10-08 8:57 ` [PATCH] qemu-nbd: Document benefit of --pid-file Max Reitz
2019-10-08 9:24 ` Daniel P. Berrangé
2019-10-08 9:40 ` Vladimir Sementsov-Ogievskiy
2019-10-08 13:28 ` Eric Blake
2019-10-08 13:38 ` Daniel P. Berrangé
2019-10-08 13:53 ` Vladimir Sementsov-Ogievskiy
2019-10-08 13:56 ` Eric Blake
2019-11-16 2:01 ` Eric Blake
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=20191007194840.29518-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).