Re: [Nbd] [w@...112...: Re: nbd-client started at boot (for root device) is not persistent]
- To: Wouter Verhelst <w@...112...>
- Cc: "nbd-general@lists.sourceforge.net" <nbd-general@lists.sourceforge.net>
- Subject: Re: [Nbd] [w@...112...: Re: nbd-client started at boot (for root device) is not persistent]
- From: Alex Bligh <alex@...872...>
- Date: Mon, 28 Nov 2016 17:49:40 +0000
- Message-id: <F3D57B0E-0514-4202-BACF-7292EAB92431@...872...>
- In-reply-to: <20161128174127.zehthzwyhofzapcj@...3...>
- References: <20161125080636.f6dsb6227ksazolh@...3...> <CAMOh2pLvgGXJ2YV4_W1bUo6VR3Mtemh8m-WYzNhhmQBt8QW3tw@...18...> <20161127162324.55mnsegroesep5td@...3...> <CAMOh2pK_rK126LNvCXzX_t9zjxFW4wJBOxJM6TenQrmeTBCXvA@...18...> <20161128174127.zehthzwyhofzapcj@...3...>
> On 28 Nov 2016, at 17:41, Wouter Verhelst <w@...112...> wrote:
>
> What I'm suggesting is that the parent process negotiates everything,
> but that it does the fork() call only just before doing the NBD_DO_IT
> ioctl(). At that point, we've already negotiated, and there is very
> little that can go wrong anymore. The child process will need to wait a
> short while to avoid the obvious race (although a second might indeed be
> overdoing it), but beyond that it should be good.
I will admit to not following this in complete detail, but this sounds
to me like a systemd problem / thinko, rather than an nbd client
thinko.
I suppose it would be possible to specify some sort of external command
that could be run when (re)mounting, or (if run under systemd) send it
some form of message ...
--
Alex Bligh
Reply to: