From owner-freebsd-stable Sat Mar 3 21:42:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 8CA8A37B71A for ; Sat, 3 Mar 2001 21:42:32 -0800 (PST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.2/8.11.2) with ESMTP id f245fJg36196; Sun, 4 Mar 2001 00:41:19 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010304003949.01cfdf40@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sun, 04 Mar 2001 00:41:18 -0500 To: Cy Schubert - ITSD Open Systems Group , nate@yogotech.com (Nate Williams) From: Mike Tancsa Subject: Re: more strange problem with broken pipes and ssh Cc: Don Lewis , stable@FreeBSD.ORG In-Reply-To: <200103040531.f245Vuc04583@cwsys.cwsent.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:31 PM 3/3/2001 -0800, Cy Schubert - ITSD Open Systems Group wrote: >In message <15009.52817.869675.390701@nomad.yogotech.com>, Nate >Williams writes >: > > > > >I wonder if this problem might be shell dependent. Maybe some shells > > > > >reset SIGPIPE to SIG_DFL and some don't modify whatever they inherit. > > > > >I'm seeing the problem with csh. What shells are everyone else > running? > > > > > > > > /bin/tcsh > > > > /bin/sh > > > > /bin/csh > > > > > > > > give me the same results. What about the grep | less example ? Can > you > > > > reproduce that ? > > > > > > > > with bash, the result is a little different. On the maillog > example, I on > > ly > > > > get one "broken pipe" at the end. > > > > > > I've tried it with bash, sh, and tcsh. I can't seem to get a SIGPIPE. > > > > I am certainly getting the error with stock csh (really tcsh). > >I don't think it's the shell. To verify my results try changing your >login shells (e.g. vipw, log out, log in, test, vipw, log out, ...) >just like I did. All this guessing will get us nowhere until more >actual testing is done. > >Could it be an sshd config option? The last time this came up a month ago, you mentioned your environment being a bit different with Kerberos. Perhaps with kerberos enabled, this problem is not there ? >X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 >Reply-to: Cy Schubert - ITSD Open Systems Group >From: Cy Schubert - ITSD Open Systems Group >X-OS: FreeBSD 4.2-RELEASE >X-Sender: cy >To: kstewart@urx.com >cc: Mike Tancsa , Dag-Erling Smorgrav , > stable@FreeBSD.ORG >Subject: Re: broken pipes on make world >In-reply-to: Your message of "Sun, 14 Jan 2001 18:41:49 PST." > <3A62636D.4DB982AD@urx.com> >Mime-Version: 1.0 >Content-Type: text/plain; charset=us-ascii >Date: Mon, 15 Jan 2001 04:25:28 -0800 >Sender: cy@uumail.gov.bc.ca >X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (amavis.org) >X-UIDL: #6b"!(R:!!A^)"!Uf&"! > >In message <3A62636D.4DB982AD@urx.com>, Kent Stewart writes: > > > > > > Mike Tancsa wrote: > > > > > > At 10:58 PM 1/14/2001 +0100, Dag-Erling Smorgrav wrote: > > > >Mike Tancsa writes: > > > > > Does anyone else get this ? > > > > > > > >Lemme guess - full disk? > > > > > > No, I have plenty of disk space on all 4 machines. I didnt see this on > > > builds from Friday. Only today. > > > > Green made a number of changes to OpenSSH on Saturday. I only have > > problems if I log in and do a make world using ssh with those changes. > > What is interesting is to use both telnet and ssh to do the following. > > The output from the ssh session is seriously truncated when it is > > doing some of the traverses. > > > > cd /usr/src/share/man > > makewhatis -v /usr/share/man > > > > It didn't have problems with man9 but there are 5 broken pipes > > traversing man8. > >I you're using X, you can su -, then xterm -ls. This creates a session >(from a process sense -- see Kirk's 4.4BSD book for details). > >If you're not using X, su - and temporarily create a /root/.rhosts file >allowing localhost access to the machine then rlogin localhost. This >will have the same effect as above. > >I personally haven't had the problems because I use krb5 rlogin and >telnet directly to root, depending on whether the packets are NATed and >VPNed or not, e.g krlogin -x -l root host or ktelnet -a -x -l root host. -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message