Date: Fri, 10 Nov 1995 18:58:52 -0800 (PST) From: "Richard W. Gross" <richg@beachnet.com> To: Pete Carah <pete@puffin.pelican.com> Cc: msmith@atrad.adelaide.edu.au, questions@freebsd.org Subject: Re: INN and FreeBSD 2.0.5 Message-ID: <Pine.LNX.3.91.951110185141.11091A-100000@frisbee.beachnet.com> In-Reply-To: <m0tDxxK-0000ReC@puffin.pelican.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, that was the trick. Although I am going to put everything on the Adaptec for 4 scsi drives, instead of two scsi and two ide's. That, and changing to bash as mentioned, should do it. I have been running inn1.4unoff3 with a crash about once a day. Machine is a P90 with 64meg, neptune motherboard. I did read in the FAQ that this motherboard has a limit of 2 bus masters and I'm running three: DEC 21140 PCI ethernet, Mach64 PCI, and the Adaptec 2940W. So maybe I do have a motherboard problem because of the three bus mastering PCI devices on a neptune motherboard. Why do things have to be so complicated?!! Thank you all very much for your input. I was able to get this box running quickly because of it. richg ___________________________________________________________________ Richard W. Gross | voice 310-823-3308 BeachNet Internet Access | fax 310-823-1390 E-mail sales: sales@beachnet.com | http://www.beachnet.com richg@beachnet.com | Dialup PPP/USR v.34 locked 115k On Fri, 10 Nov 1995, Pete Carah wrote: > In article <199511090030.AAA08171@genesis.atrad.adelaide.edu.au> you write: > > >Richard W. Gross stands accused of saying: > >> I have problems with my news machine with the following: > -- > >> Nov 8 14:20:16 inout /kernel: pid 21668: sh: uid0: exited on signal 11 > >> --- > > >Sounds like hardware problems; sig11 is a great indicator of bad memory. > > If he's running INN, it is a well-known problem; you can't run innwatch > with the freebsd default shell; you *MUST* use bash (maybe pdksh, but > bash certainly works). (there is apparently a problem with how ash > handles IFS; there may be more problems too; several INN scripts count > on non-standard IFS and innwatcch is one of them). > > >> And one of the hard drives starts seeking back and forth... > > >Is it actually doing anything? > Yes, saving core files of the shell about once/second. Good for keeping > nearly anything else from happening. > > >> Any ideas what this means? > > >What hardware are you running? > > Not relevant. Go and put #!/bin/bash (or whatever your path to bash is) > in the top of *all* the INN scripts in place of #! /bin/sh and the > problem will go away. > > This should be documented in our port of INN (which I have never used, > preferring to customize a bit from the distribution so as to get > the streaming patch in and such.) > > -- Pete >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.3.91.951110185141.11091A-100000>