lkml.org 
[lkml]   [1997]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [rfc] posix.4 signals implementation
Date
To: linux-kernel@vger.rutgers.edu
Subject: Re: [rfc] posix.4 signals implementation
X-Newsreader: TIN [UNIX 1.3 950515BETA PL0]

Richard Henderson wrote:
: There are known problems building nfs, lockd, autofs, etc because
: they muck with signals in nasty ways and it is not clear to me what
: is intended, especially in the presense of queued signals. My first
: reaction is why should they have to be mucking with SIGPIPE anyway?

Because when e.g. a mount client dies and mountd attempts to write
to the socket, it receives a SIGPIPE. Both mountd and the user-space nfsd
both re-read the exports file on SIGHUP, and unfsd also needs SIGALRM
to clean up its file handle cache occasionally. What is it exactly
that gives you headaches?

Olaf
--
Olaf Kirch | XmToggleButton resource set; class Set; values set/unset
okir@monad.swb.de | Motif for Quiche Eaters

\
 
 \ /
  Last update: 2005-03-22 13:39    [W:0.963 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site