Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!in2.uu.net!news.tacom.army.mil!reason.cdrom.com!usenet From: "Jordan K. Hubbard" <jkh@FreeBSD.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Problems with 2.2-960130-SNAP Date: Wed, 14 Feb 1996 02:28:54 -0800 Organization: Walnut Creek CDROM Lines: 34 Message-ID: <3121B966.2781E494@FreeBSD.org> References: <ngsxXaw@quack.kfu.com> <4fprr7$oq8@godzilla.zeta.org.au> NNTP-Posting-Host: time.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.0 (X11; I; FreeBSD 2.1-STABLE i386) Bruce Evans wrote: > In article <ngsxXaw@quack.kfu.com>, Nick Sayer <nsayer@quack.kfu.com> wrote: > >... > >2. Something has gone wrong with rshd -- it never exits after a job > >has completed. Substituting the 2.1.0-RELEASE rshd doesn't help any. > >This problem is really painful, since it's screwing up the backups > >(this machine is the tapehost). > > This was caused by selecting on pipes being broken. Replace kern/sys_pipe.c I just wanted to take this opportunity to also make an often-made and often-ignored point: If you are going to run 2.2-CURRENT, you MUST MUST MUST join and promise to frequently read the freebsd-current@freebsd.org mailing list. This is simply indispensible since you'll otherwise be bitten at every turn by unexpected changes to the system. That's what running on the bleeding edge is all about, and if you're going to go intentionally into harms way, go at least well informed and prepared! :-) http://www.freebsd.org/handbook/current.html has a more complete synopsis of what -current is all about, and how to survive life there. In Nick's particular case, the extensive performance changes to the pipe code (and the chronicle of their subsequent return to health) was discussed over several days, and this might have at least let Nick know why he was getting hosed and when it was time to grab the necessary bug fixes. Not to single Nick out here or anything, I'm not. I'm simply trying to illustrate his example in what is hopefully an educational context.. :-) -- - Jordan Hubbard President, FreeBSD Project