Re: [Nbd] NBD server terminates on SIGPIPE during negotiation
- To: Wouter Verhelst <w@...112...>
- Cc: nbd-general@lists.sourceforge.net, Juha Erkkilä <juha.erkkila@...1258...>, Tuomas Räsänen <tuomasjjrasanen@...1258...>, Veli-Matti Lintu <vmlintu@...1258...>
- Subject: Re: [Nbd] NBD server terminates on SIGPIPE during negotiation
- From: Alex Bligh <alex@...872...>
- Date: Thu, 7 Feb 2013 14:03:22 +0000
- Message-id: <845EDAF1-D174-4340-ACCA-589E75322F24@...872...>
- In-reply-to: <20130206213827.GG23267@...3...>
- References: <906386062.29057.1359357352016.JavaMail.root@...1258...> <2100839723.30677.1359363466317.JavaMail.root@...1258...> <20130205213747.GD23949@...3...> <948275DB-73FC-4448-A164-E2B8FE27177B@...872...> <20130206213827.GG23267@...3...>
On 6 Feb 2013, at 21:38, Wouter Verhelst wrote:
> This situation is of course different if the server is not using a
> fork-per-client paradigm; but since that's what we're doing, I fail to
> see any benefit in ignoring SIGPIPE, while there is some benefit to be
> had in not ignoring it.
OK - so this is assuming you fork prior to the negotiation?
In which case no objections here assuming we never do any activity
on any /other/ fd which is likely to cause a SIGPIPE. If you kill
syslogd, does logging stuff to syslog ever cause a SIGPIPE for instance?
It would be bad if failure to log something caused a disk to drop off.
--
Alex Bligh
Reply to: