Date: Wed, 30 Jun 2010 09:34:47 -0400 From: John Baldwin <jhb@freebsd.org> To: Ed Schouten <ed@80386.nl> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r209595 - head/sys/kern Message-ID: <201006300934.47629.jhb@freebsd.org> In-Reply-To: <20100629210522.GY2179@hoeg.nl> References: <201006292044.o5TKiJd7031766@svn.freebsd.org> <20100629210522.GY2179@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 29 June 2010 5:05:22 pm Ed Schouten wrote: > * John Baldwin <jhb@FreeBSD.org> wrote: > > Log: > > Send SIGPIPE to the thread that issued the offending system call > > rather than to the entire process. > > Should something similar be used inside the TTY layer, where > reads/writes may cause signals to be generated? Hmm, I'm not sure. I do think you want to stop the entire process for SIGTTOU or SIGTTIN (often the entire process group it seems), so I'm not sure if it matters if the signal is sent to only the current thread versus sending it to any thread in the process. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201006300934.47629.jhb>