Re: [Nbd] [PATCH] nbd-server: add -D/-dont-daemonize option
- To: "Dmitry V. Levin" <ldv@...1147...>
- Cc: nbd-general@lists.sourceforge.net
- Subject: Re: [Nbd] [PATCH] nbd-server: add -D/-dont-daemonize option
- From: Goswin von Brederlow <goswin-v-b@...186...>
- Date: Mon, 25 Jun 2012 11:59:44 +0200
- Message-id: <87pq8n1zlb.fsf@...860...>
- In-reply-to: <20120624230358.GA28298@...1147...> (Dmitry V. Levin's message of "Mon, 25 Jun 2012 03:03:58 +0400")
- References: <20120624230358.GA28298@...1147...>
"Dmitry V. Levin" <ldv@...1147...> writes:
> + <term><option>-D</option></term>
> + <listitem>
> + <para>Do not detach and do not become a daemon. This allows
> + easy monitoring by service managers like systemd.</para>
> + </listitem>
> + </varlistentry>
> + <varlistentry>
> <term><option>-d</option></term>
> <listitem>
> - <para>Do not fork. Useful for debugging.</para>
> + <para>Do not fork at all. Useful for debugging.</para>
> </listitem>
> </varlistentry>
> <varlistentry>
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
connect, right?
Also why should systemd care? It uses cgroups to monitor services. Isn't
that one of the advantages of systemd over all the other service
monitors?
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).
MfG
Goswin
Reply to: