Date: Fri, 10 Nov 95 10:13 PST From: pete@puffin.pelican.com (Pete Carah) To: msmith@atrad.adelaide.edu.au Cc: questions@freebsd.org Subject: Re: INN and FreeBSD 2.0.5 Message-ID: <m0tDxxK-0000ReC@puffin.pelican.com> In-Reply-To: <199511090030.AAA08171@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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?m0tDxxK-0000ReC>