Messages in this thread | | | From | (Olaf Kirch) | Subject | Re: [rfc] posix.4 signals implementation | Date | Thu, 15 May 1997 15:45:20 +0200 (MET DST) |
| |
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
| |