Re: [Nbd] nbd-client and SIGSTOP/SIGCONT
- To: paul.clements@...856...
- Cc: nbd-general@lists.sourceforge.net
- Subject: Re: [Nbd] nbd-client and SIGSTOP/SIGCONT
- From: Wouter Verhelst <w@...112...>
- Date: Sun, 1 May 2011 16:06:56 +0200
- Message-id: <20110501140656.GB13498@...510...>
- In-reply-to: <BANLkTikGvXxOjixr15be1dQwKcXQ-+mYMg@...18...>
- References: <18F04FC1323C451FAA5F1A46D91AFEF3@...867...> <BANLkTikhxVX0QTQaCTrW4P8fL42m9a4s1g@...18...> <1E2BDAB96EA24FC4B8B6C9D43D0E1CE7@...867...> <BANLkTikGvXxOjixr15be1dQwKcXQ-+mYMg@...18...>
On Mon, Apr 18, 2011 at 10:02:35PM -0400, Paul Clements wrote:
> On Mon, Apr 18, 2011 at 11:44 AM, Ian <coughlan@...866...> wrote:
>
> > Thanks for the patch. This same thing was the first thing I tried, but
> > quickly realized that more was needed. When -ERESTARTSYS is returned
> > (without first shutting down the socket), we re-enter the ioctl, create
> > another thread, and that thread prints out "nbd3: wrong magic", terminates,
> > and we return -EPROTO to the client, which also terminates, and the block IO
> > is hosed.
>
> Ah, yep....
>
> > I think I might just hack killall5 for now, to prevent it from sending the
> > SIGSTOP/SIGCONT to nbd.
>
> That is not a bad idea. A much easier hack than making nbd-client
> re-entrant, I must admit.
It's basically what I do to make root-on-NBD work in Debian; there's a
/lib/init/rw/sendsigs.omit.d directory in Debian where you can write PID
files for processes that you don't want killall5 to destroy.
--
The volume of a pizza of thickness a and radius z can be described by
the following formula:
pi zz a
Reply to: