Date: Mon, 9 Aug 2010 12:26:45 -0400 From: Wesley Shields <wxs@FreeBSD.org> To: Alex Kozlov <spam@rm-rf.kiev.ua> Cc: freebsd-bugs@FreeBSD.org, Ruben van Staveren <ruben@verweg.com> Subject: Re: kern/148781: [kernel] SIGPIPE after update to 8.1-RC2 Message-ID: <20100809162645.GB19844@atarininja.org> In-Reply-To: <20100809154755.GA56696@ravenloft.kiev.ua> References: <20100809154755.GA56696@ravenloft.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 09, 2010 at 06:47:55PM +0300, Alex Kozlov wrote: > On Mon, Aug 09, 2010 at 03:10:09PM +0000, Ruben van Staveren wrote: > > > > I'm revoking this pr. Discussion on the mailinglist suggest this is a = > > bug in sudo > Its need to be reassigned to ports category. > > > After sudo > > > > (0|root@helium|pts/1[*]) ...mail/moztraybiff # procstat -i $$ | grep PIP > > 15982 tcsh PIPE -I- > > (0|root@helium|pts/1[*]) ...mail/moztraybiff # make fetch > > grep: write error: Broken pipe > > =3D=3D=3D> License check disabled, port has not defined LICENSE > > (0|root@helium|pts/1[*]) ...mail/moztraybiff #=20 > > > > after su > > > > (0|helium|pts/2[1]) ~ > su - root > > Password: > > helium# procstat -i $$ | grep PIP > > 16011 csh PIPE --- > > helium# cd /usr/ports/mail/moztraybiff/ > > helium# make fetch > > =3D=3D=3D> License check disabled, port has not defined LICENSE > > helium#=20 > > > > > > Even more, on some occasions sudo also will display the empty set for = > > PIPE. However, it is non trivial to provoke that state. > > An upgrade to sudo 1.7.4 might solve this to. A quick test showed a much = > > more likeness with su regarding "procstat -i $$ | grep PIPE" behavior = > > but I haven't extensively tested this. > I make local port for sudo 1.7.4 and after upgrading I don't have PIPE > problem anymore, at least with portsnap/make missing. Thanks for bringing this to my attention. I intend to update the sudo port to 1.7.4p2 sometime this week. I've been traveling for work/vacation the past week and a half so I have not had time to get to it until now. Hopefully the update will resolve this issue. -- WXS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100809162645.GB19844>