Re: [Nbd] [PATCH] nbd-server: add -D/-dont-daemonize option
- To: Goswin von Brederlow <goswin-v-b@...186...>, "Dmitry V. Levin" <ldv@...1147...>
- Cc: email@example.com
- Subject: Re: [Nbd] [PATCH] nbd-server: add -D/-dont-daemonize option
- From: Alex Bligh <alex@...872...>
- Date: Mon, 25 Jun 2012 17:29:45 +0100
- Message-id: <B8A6F0F1B1B6592D21C27562@...873...>
- Reply-to: Alex Bligh <alex@...872...>
- In-reply-to: <87pq8n1zlb.fsf@...860...>
- References: <20120624230358.GA28298@...1147...> <87pq8n1zlb.fsf@...860...>
--On 25 June 2012 11:59:44 +0200 Goswin von Brederlow <goswin-v-b@...186...>
I think the difference between -D and -d should be made clearer.
With -d the server runs in the foreground and accepts a single
connection only and outputs debug infos, right?
With -D the server runs in the foreground but forks a child for every
Agree re documentation point - must admit it had me confused, but ...
What I would like to see is socket activation in nbd-server. That way
the service can be started as needed without performance loss (other
than the initial startup time once).
Doesn't this only affect connect time, which given the connections are
very long lasting isn't of vast importance? In any case, the fact the patch
doesn't do X extra feature would not be a reason to reject it (not sure
you were suggesting that).