From owner-freebsd-isp Sun Nov 30 10:23:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA23298 for isp-outgoing; Sun, 30 Nov 1997 10:23:53 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from user.xtdl.com (user.xtdl.com [206.25.228.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA23280 for ; Sun, 30 Nov 1997 10:23:49 -0800 (PST) (envelope-from sderdau@xtdl.com) Received: from user.xtdl.com (user.xtdl.com [206.25.228.20]) by user.xtdl.com (8.6.11/8.6.9) with SMTP id NAA27589 for ; Sun, 30 Nov 1997 13:45:56 -0500 Date: Sun, 30 Nov 1997 13:45:56 -0500 (EST) From: "Stephen A. Derdau" To: freebsd-isp@freebsd.org Subject: Re: Adaptec 2940 and FreeBSD 2.2.2-RELEASE In-Reply-To: <199711281446.JAA28643@bilver.magicnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We'll I can say the Adptec does work with FreeBSD 2.2.5. After 3 or 4 days messing with the installation I finally stumbled upon the problem when loading FreeBSD for the uptenth time. I could install off the cdrom . However, once it went to boot on it's own I would get a fatal error message after it cofigured sc0. Too bad I don't know enogh about this stuff yet. Trial and error I guess. But anyways I stumbled upon the 3com card problem after many many tries. I had to disable the memory on the card. My next step is to try the memory address that is recommended for Intel16 cards, D000008 or something. Hope that works as far as the 3com card goes. ******* But I did want to say that the ADAPTEC 2940 appears ******* to be working with FreeBSD 2.2.5 . As for swithcing ******* to another OS that someone mentioned. From all I've heard ******* I'm sticking with FreeBSD. Thanks FreeBSD for the great OS you People are Providing Happy Holidays to all !!! Thank You Stephen A. Derdau XTDL inc 10 Chestnut Dr. Bedford, NH 03110 603 4714700 "If it wasn't for something I would have nothing!:)" From owner-freebsd-isp Sun Nov 30 11:21:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA27096 for isp-outgoing; Sun, 30 Nov 1997 11:21:18 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA27091 for ; Sun, 30 Nov 1997 11:21:12 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id LAA23377; Sun, 30 Nov 1997 11:23:24 -0800 (PST) Message-Id: <199711301923.LAA23377@implode.root.com> To: "Stephen A. Derdau" cc: freebsd-isp@FreeBSD.ORG Subject: Re: Adaptec 2940 and FreeBSD 2.2.2-RELEASE In-reply-to: Your message of "Sun, 30 Nov 1997 13:45:56 EST." From: David Greenman Reply-To: dg@root.com Date: Sun, 30 Nov 1997 11:23:24 -0800 Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >upon the problem when loading FreeBSD for the uptenth time. >I could install off the cdrom . However, once it went to boot on it's own >I would get a fatal error message after it cofigured sc0. Do you recall what the message said? >But anyways I stumbled upon the 3com card problem after many many tries. >I had to disable the memory on the card. My next step is to try >the memory address that is recommended for Intel16 cards, D000008 or >something. Hope that works as far as the 3com card goes. I think you mean 0xd8000. In any case, make sure that the kernel configuration agrees with the setting of the card. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-isp Mon Dec 1 03:17:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA00604 for isp-outgoing; Mon, 1 Dec 1997 03:17:03 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from axe.cablenet.net (axe.cablenet.net [194.154.36.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA00594 for ; Mon, 1 Dec 1997 03:16:56 -0800 (PST) (envelope-from damian@axe.cablenet.net) Received: from axe (localhost [127.0.0.1]) by axe.cablenet.net (8.8.7/8.6.9) with SMTP id LAA14138; Mon, 1 Dec 1997 11:13:11 GMT Message-ID: <34829BC7.41C67EA6@cablenet.net> Date: Mon, 01 Dec 1997 11:13:11 +0000 From: Damian Hamill Organization: CableNet Ltd X-Mailer: Mozilla 3.0 (X11; I; SunOS 4.1.4 sun4m) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: freebsd-isp@freebsd.org Subject: Re: Adaptec 2940 and FreeBSD 2.2.2-RELEASE References: <199711281446.JAA28643@bilver.magicnet.net> <199711282008.NAA11788@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs wrote: > > Good cables are a must. However .5m cables (if you have multiple > > targets) is definately not SCSI spec, which is .3m between targets > > and .1m stub. > > People missunderstand the SCSI spec all of the time. In part this is > because this section is poorly written. The main thing to come out > of the stub/device spacing requirement is the minimum 3 to 1 ratio. > For internal cabling configurations, your stub length is determined > by the PCB tracings on the drive's electronic board which is typically > less than .05m. This means you can actually cluster devices fairly > close together. Even more important than device spacing length is > spacing consistency, having devices and cables with similar loads, > termination, and overall cable length. I'd like to understand this better so in future I can make sure I get the cables just right. We have a ribbon cable in an external drive array with 4 drive connectors spaced ~15cm apart and 50 pin centronic connectors on either end. The long end connects to the external cable which goes to the external port of the SCSI adaptor and the short end has a terminator, so it looks like this. [3940]--- | | .5m external cable | | [50 pin centronics connectors] | | .3m SCSI ribbon cable | | = drive connector 1 | .15m cable | = drive connector 2 | ...... | = drive connector 4 | .07m | [50 pin centronics connector] [terminator] It's working fine at Ultra SCSI speed but I'd like to know whether I can make these cables any better by changing any of the cable section lengths. We used one of those 8 connector SCSI cables as a starting point and chopped it in half so thats how we came to have the ~15cm spacing with the short end at the terminator. The only section I can make shorter is the external cable (down to about .35m). regards damian -- * Damian Hamill M.D. damian@cablenet.net * CableNet & The Landscape Channel * http://www.cablenet.net/ http://www.landscapetv.com/ From owner-freebsd-isp Mon Dec 1 03:23:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA01067 for isp-outgoing; Mon, 1 Dec 1997 03:23:36 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from chain.freebsd.os.org.za (zhqW4uV62S5w95cJGIGucZEwTealuro4@chain.iafrica.com [196.7.74.174]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA00854 for ; Mon, 1 Dec 1997 03:20:07 -0800 (PST) (envelope-from khetan@chain.iafrica.com) Received: from localhost (khetan@localhost) by chain.freebsd.os.org.za (8.8.8/8.8.8) with SMTP id NAA04655; Mon, 1 Dec 1997 13:17:01 +0200 (SAT) Date: Mon, 1 Dec 1997 13:17:01 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@chain Reply-To: Khetan Gajjar To: "Jan L. Peterson" cc: isp@freebsd.org Subject: Re: Adding 700+ users with one or two commands In-Reply-To: <199711191826.LAA10409@banana.imall.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Jan L. Peterson wrote: >while read line > do eval set $line > adduser -batch $1 $2 "" "$4" $5 -shell nologin > done < yourfile Great. It worked :) I ended up using while read line; do eval set $line; adduser -batch $1 "" "" $3 "$4" $5 -shell nologin; done < input_file --- Khetan Gajjar - whois kg1779 | khetan@iafrica.com or khetan@os.org.za http://chain.iafrica.com/~khetan | PGPKey : finger khetan@chain.iafrica.com UUNET Internet Africa Support | FreeBSD enthusiast-www2.za.freebsd.org Unix is user friendly; it's just selective about who it calls a friend! From owner-freebsd-isp Mon Dec 1 04:33:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA04630 for isp-outgoing; Mon, 1 Dec 1997 04:33:18 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from ot.stpn.soft.net (freebie.opentech.stpn.soft.net [204.143.126.74]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA04602 for ; Mon, 1 Dec 1997 04:33:12 -0800 (PST) (envelope-from pdongre@opentech.stpn.soft.net) Received: from andes (andes.opentech.stpn.soft.net [204.143.126.66]) by ot.stpn.soft.net (8.6.12/8.6.12) with ESMTP id SAA07959 for ; Mon, 1 Dec 1997 18:05:13 +0530 Message-ID: <34834181.99CEC749@opentech.stpn.soft.net> Date: Mon, 01 Dec 1997 18:00:18 -0500 From: Prashant Dongre Reply-To: pdongre@opentech.stpn.soft.net X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-isp@FreeBSD.ORG Subject: multiport sync cards for freebsd.... X-Priority: 3 (Normal) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Can anyone tell me about multiport sync cards manufacturers supporting 56/64 Kbps and upwards apart from Emerging Tech and SDL. TIA Prashant. From owner-freebsd-isp Mon Dec 1 11:41:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA07332 for isp-outgoing; Mon, 1 Dec 1997 11:41:41 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from ucet.ufl.edu (ronell.ucet.ufl.edu [128.227.243.237]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA07316 for ; Mon, 1 Dec 1997 11:41:36 -0800 (PST) (envelope-from northrup@ucet.ufl.edu) Received: from localhost (northrup@localhost) by ucet.ufl.edu (8.7.5/8.6.9) with SMTP id OAA94006 for ; Mon, 1 Dec 1997 14:41:11 -0500 Date: Mon, 1 Dec 1997 14:41:10 -0500 (EST) From: Dylan Northrup To: freebsd-isp@freebsd.org Subject: NIS setup question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok, I've got my FreeBSD box ('kubrick' which is running 2.2.2 on a Pentium Pro 200 with 128 Megs of RAM) set up as an NIS master server. I've also got a machine ('jms' which is running AIX 4.2) set up as a client machine. There are no slave servers. The passwd file that I'm distributing via NIS is not the master.passwd file for the server, but instead a version that sits in /etc/nis. The client is able to see the maps that are coming from the server. However, when I try to use yppasswd on the client, strange things happen. The NIS maps seem to reflect the change (i.e. logging into the client after running yppasswd, I have to use the new password) but the original file is not changed. Also, when I run yppasswd, I get the following error messages. . . Enter the new password again: 3004-622 An error occurred updating the password database. 3004-604 Your entry does not match the old password. yppasswd: 1831-155 could not change passwd Now, if I use yppasswd and give it the same password for the new password as the old password, I get this... Enter the new password again: 3004-622 An error occurred updating the password database. northrup's New password: Enter the new password again: And I put in the new password again, then it exits. I'm using the following for my rpc.yppasswdd command... /usr/sbin/rpc.yppasswd -t /etc/nis/master.passwd -s -f Anyone have any pointers on what I might be doing incorrectly? -- Dylan Northrup <*> northrup@nwe.ufl.edu <*> http://web.nwe.ufl.edu/~northrup <*> --------------- Random B5 Quote "Curious. We have the memories of your entire life to play with, but your thoughts are rooted here in this station. It means a lot to you, doesn't it?" -- Knight Two, "And The Sky Full Of Stars" From owner-freebsd-isp Mon Dec 1 12:47:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA15026 for isp-outgoing; Mon, 1 Dec 1997 12:47:14 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from toth.ferginc.com (toth.ferginc.com [205.139.23.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA15018 for ; Mon, 1 Dec 1997 12:47:11 -0800 (PST) (envelope-from branson@toth.ferginc.com) Received: (from branson@localhost) by toth.ferginc.com (You_Can/Keep_Guessing) id PAA22669; Mon, 1 Dec 1997 15:45:30 -0500 (EST) Message-ID: <19971201154530.12200@toth.FergInc.com> Date: Mon, 1 Dec 1997 15:45:30 -0500 From: Branson Matheson To: Dylan Northrup Cc: freebsd-isp@FreeBSD.ORG Subject: Re: NIS setup question Reply-To: Branson.Matheson@FergInc.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Dylan Northrup on Mon, Dec 01, 1997 at 02:41:10PM -0500 Organization: Ferguson Enterprises, Inc. X-Operating-System: FreeBSD 2.2.2-RELEASE Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Dec 01, 1997 at 02:41:10PM -0500, Dylan Northrup wrote: > I'm using the following for my rpc.yppasswdd command... > > /usr/sbin/rpc.yppasswd -t /etc/nis/master.passwd -s -f > > Anyone have any pointers on what I might be doing incorrectly? Add the -v flag so that we can see the updates. - branson ------------------------------------------------------------------------------- Branson Matheson " If you are falling off of a mountain, Unix System Administrator You may as well try to fly." Ferguson Enterprises, Inc. - Delenn, Mimbari Ambassador ( $statements = ) !~ /Corporate Opinion/; From owner-freebsd-isp Mon Dec 1 23:17:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA06197 for isp-outgoing; Mon, 1 Dec 1997 23:17:43 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from lily.ezo.net (root@lily.ezo.net [206.102.130.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA06146; Mon, 1 Dec 1997 23:17:32 -0800 (PST) (envelope-from jflowers@ezo.net) Received: from lily.ezo.net (jflowers@localhost.ezo.net [127.0.0.1]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id CAA24479; Tue, 2 Dec 1997 02:17:15 -0500 (EST) Date: Tue, 2 Dec 1997 02:17:15 -0500 (EST) From: Jim Flowers To: skip-info@skip.org, freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org, freebsd-ports@freebsd.org, freebsd-security@freebsd.org, freebsd-test@freebsd.org cc: "Matthew N. Dodd" Subject: Skip 1.0 for FreeBSD 2.5.5 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Patches for Skip Source Release 1.0 that compile cleanly on FreeBSD 2.5.5 are available from http://www.vip-link.com/pub/vip/skip/. Initial tests indicate all functions work including skiptool with X-windows (except for pop-up display of statistics). Please feel free to download and use. Email any comments or bug reports to my attention. Jim Flowers #4 ISP on C|NET, #1 in Ohio From owner-freebsd-isp Mon Dec 1 23:42:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA08103 for isp-outgoing; Mon, 1 Dec 1997 23:42:38 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA08098 for ; Mon, 1 Dec 1997 23:42:31 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.8/8.8.7) id JAA06994; Tue, 2 Dec 1997 09:36:40 +0200 (SAT) From: John Hay Message-Id: <199712020736.JAA06994@zibbi.mikom.csir.co.za> Subject: Re: multiport sync cards for freebsd.... In-Reply-To: <34834181.99CEC749@opentech.stpn.soft.net> from Prashant Dongre at "Dec 1, 97 06:00:18 pm" To: pdongre@opentech.stpn.soft.net Date: Tue, 2 Dec 1997 09:36:40 +0200 (SAT) Cc: freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Can anyone tell me about multiport sync cards manufacturers supporting 56/64 > Kbps and upwards apart from Emerging Tech and SDL. There is also the Digi/Arnet SYNC/570i cards that use the ar(4) device driver and the Cronyx-Sigma cards that use the cx(4) driver. I haven't used the Cronyx cards though, so I don't don't know how easily you can get them. Digi has got an web site at: http://www.dgii.com/ John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-isp Tue Dec 2 11:30:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25858 for isp-outgoing; Tue, 2 Dec 1997 11:30:29 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from ucet.ufl.edu (ronell.ucet.ufl.edu [128.227.243.237]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA25848 for ; Tue, 2 Dec 1997 11:30:26 -0800 (PST) (envelope-from northrup@ucet.ufl.edu) Received: from localhost (northrup@localhost) by ucet.ufl.edu (8.7.5/8.6.9) with SMTP id OAA105790; Tue, 2 Dec 1997 14:30:13 -0500 Date: Tue, 2 Dec 1997 14:30:13 -0500 (EST) From: Dylan Northrup To: Branson Matheson cc: freebsd-isp@FreeBSD.ORG Subject: Re: NIS setup question In-Reply-To: <19971201154530.12200@toth.FergInc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Dec 1997, Branson Matheson wrote: :=On Mon, Dec 01, 1997 at 02:41:10PM -0500, Dylan Northrup wrote: :=> I'm using the following for my rpc.yppasswdd command... :=> :=> /usr/sbin/rpc.yppasswd -t /etc/nis/master.passwd -s -f :=> :=> Anyone have any pointers on what I might be doing incorrectly? := := Add the -v flag so that we can see the updates. Exactly what information would you like to have from this? And which files do you want me to look in for updates (aside from /var/log/messages)? -- Dylan Northrup <*> northrup@nwe.ufl.edu <*> http://web.nwe.ufl.edu/~northrup <*> --------------- Random B5 Quote "Jumpgate activated. Here they come." -- Lieutenant David Corwin, "Point of No Return" From owner-freebsd-isp Tue Dec 2 12:37:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01314 for isp-outgoing; Tue, 2 Dec 1997 12:37:06 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01269; Tue, 2 Dec 1997 12:36:45 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA05734; Tue, 2 Dec 1997 12:36:12 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma005730; Tue Dec 2 12:35:58 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id MAA02228; Tue, 2 Dec 1997 12:35:58 -0800 (PST) From: Archie Cobbs Message-Id: <199712022035.MAA02228@bubba.whistle.com> Subject: Re: Skip 1.0 for FreeBSD 2.5.5 In-Reply-To: from Jim Flowers at "Dec 2, 97 02:17:15 am" To: jflowers@ezo.net (Jim Flowers) Date: Tue, 2 Dec 1997 12:35:57 -0800 (PST) Cc: skip-info@skip.org, freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org, freebsd-ports@freebsd.org, freebsd-security@freebsd.org, freebsd-test@freebsd.org, winter@jurai.net X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jim Flowers writes: > Patches for Skip Source Release 1.0 that compile cleanly on FreeBSD 2.5.5 > are available from http://www.vip-link.com/pub/vip/skip/. Initial tests > indicate all functions work including skiptool with X-windows (except for > pop-up display of statistics). Please feel free to download and use. Email > any comments or bug reports to my attention. FYI- [Jim and I are in contact already regarding this] I'm working on a FreeBSD port of skip-1.0. This is somewhat involved because it requires modload'ing the kernel module, installing an rc script, etc. Hopefully will be done soon. Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-isp Wed Dec 3 05:29:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA08004 for isp-outgoing; Wed, 3 Dec 1997 05:29:52 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from wopr.inetu.net (wopr.inetu.net [207.18.13.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA07988; Wed, 3 Dec 1997 05:29:47 -0800 (PST) (envelope-from dev@wopr.inetu.net) Received: from localhost (dev@localhost) by wopr.inetu.net (8.8.5/8.8.5) with SMTP id IAA17981; Wed, 3 Dec 1997 08:36:21 -0500 (EST) Date: Wed, 3 Dec 1997 08:36:21 -0500 (EST) From: Dev Chanchani To: freebsd-questions@freebsd.org cc: freebsd-isp@freebsd.org Subject: MD5 vs. DES Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk WHen I install servers, I don't select any options when it asks for additional encryptions services (des, kerb, etc) during install. We have frontpage 3.0 (98 extensions) setup and they seem to create des passwords by default. I beleive our systems (not selecting any options) installs md5 libcrypt. So frontpage never works after I setup a web, I have to go use htpasswd to create a new password again, then everythign works. Can I dropin a new libcrypt, do a make world or something to solve this compadibability issue on a running server? Should I just re-compile htpasswd and httpd to use des (is this possible with libcrypt using md5). Any help would be greatly appreciated. Dev Chanchani - INetU, Inc.(tm) - http://www.INetU.net dev@inetu.net - Ph: (610) 266-7441 - Fx: (610) 266-7434 Web Development - Electronic Commerce - Web Hosting From owner-freebsd-isp Thu Dec 4 12:18:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA24904 for isp-outgoing; Thu, 4 Dec 1997 12:18:42 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA24890; Thu, 4 Dec 1997 12:18:38 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id MAA05014; Thu, 4 Dec 1997 12:18:33 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Thu, 4 Dec 1997 12:18:33 -0800 (PST) From: Doug White Reply-To: Doug White To: Dev Chanchani cc: freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: MD5 vs. DES In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 3 Dec 1997, Dev Chanchani wrote: > > WHen I install servers, I don't select any options when it asks for > additional encryptions services (des, kerb, etc) during install. > > We have frontpage 3.0 (98 extensions) setup and they seem to create des > passwords by default. I beleive our systems (not selecting any options) > installs md5 libcrypt. So frontpage never works after I setup a web, I > have to go use htpasswd to create a new password again, then everythign > works. > > Can I dropin a new libcrypt, do a make world or something to solve this > compadibability issue on a running server? Should I just re-compile > htpasswd and httpd to use des (is this possible with libcrypt using md5). Just install the des distribution from the install media. The DES crypt library understands MD5 so you don't need to convert your passwords. YOu may need to rebuild some stuff if you want it to use DES vice MD5. cd /; cat des.* | tar xzf - Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-isp Thu Dec 4 23:36:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA27233 for isp-outgoing; Thu, 4 Dec 1997 23:36:00 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from vsg.mobistar.be (vsg.mobistar.be [195.61.128.100]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA27219 for ; Thu, 4 Dec 1997 23:35:56 -0800 (PST) (envelope-from Gaetan@vsg.mobistar.be) Received: from Gaetan.mobistar.be (gaetan.mobistar.be [175.175.61.167]) by vsg.mobistar.be (8.8.3/8.8.3) with SMTP id IAA01997 for ; Fri, 5 Dec 1997 08:40:17 GMT Message-Id: <3.0.32.19971205083748.00ae0640@vsg.mobistar.be> X-Sender: gaetan@vsg.mobistar.be X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Fri, 05 Dec 1997 08:37:52 +0100 To: freebsd-isp@FreeBSD.ORG From: Gaetan Feige Subject: User security Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA27225 Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am wondering what is the best way to give a user access to email on a bsd box and block him from anything else like telnet, ftp into his account... Any documents on this ? Thank you Gaétan Feige (Mobistar mobile phone Operator) Tél : +32 2 745 7913 Fax : +32 2 745 7070 Mobile : +32 95 557913 E-mail:Gaetan@vsg.mobistar.be HTTP://vsg.mobistar.be/~gaetan From owner-freebsd-isp Fri Dec 5 02:09:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA09871 for isp-outgoing; Fri, 5 Dec 1997 02:09:30 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from omnix.net (root@omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA09854; Fri, 5 Dec 1997 02:09:23 -0800 (PST) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost [127.0.0.1]) by omnix.net (8.8.5/8.8.5) with SMTP id KAA17199; Fri, 5 Dec 1997 10:09:18 GMT Date: Fri, 5 Dec 1997 11:09:18 +0100 (CET) From: Didier Derny To: isp@freebsd.org, hackers@freebsd.org Subject: HELP! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm really sorry to disturb you with this message but I need a urgent help to configure a cisco 1600 router. I'm trying to connect a small network to internet through a ISDN connection (128Kb 2 B channels) I've the following data. - the router is a Cisco 1603 with 1 BRI S/T interface. - IOS 11.2 - Phone number: 0561163290 - Login: omnix - Password: xxxxx - Network: 194.149.170.24/29 (255.255.255.248) - Routeur: 194.149.170.25 - Default route: 194.149.170.1 - Primary DNS: 194.149.160.9 - Secondary DNS: 194.149.160.2 This router will be used to broadcast (video+sound with realaudio) the annual congres of a teacher union on: www.fsu.fr I know that this message is not related to freebsd. Thanks for your help. -- Didier Derny didier@omnix.net From owner-freebsd-isp Fri Dec 5 03:07:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA14398 for isp-outgoing; Fri, 5 Dec 1997 03:07:36 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from axe.cablenet.net (axe.cablenet.net [194.154.36.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA14392 for ; Fri, 5 Dec 1997 03:07:29 -0800 (PST) (envelope-from damian@axe.cablenet.net) Received: from axe (localhost [127.0.0.1]) by axe.cablenet.net (8.8.7/8.6.9) with SMTP id LAA07205 for ; Fri, 5 Dec 1997 11:03:51 GMT Message-ID: <3487DF96.62319AC4@cablenet.net> Date: Fri, 05 Dec 1997 11:03:50 +0000 From: Damian Hamill Organization: CableNet Ltd X-Mailer: Mozilla 3.0 (X11; I; SunOS 4.1.4 sun4m) MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: slow news server Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a news reader machine that is unable to keep up with the a single incoming feed. The feeder machine is running diablo and a large backlog is building up in the outbound queue. Both the feeder and the reader are similar systems System: PPro 200MHZ 256MB RAM Adaptec 3940 2 GB SCSI system disk 512 MB swap 8 x 2GB SCSI disks ccd'd to make up spool partition 4 disks on channel A and 4 on channel B history (125 MB) lives on the system disk server: innd 1.5.1 innd runs with a priority of -6 and seems to spend most of it's time in biowait state. The system is 95% idle most of the time. There is a crossover cable between the feeder machine and the reader machine so they have a private network and I'm able to transfer data via ftp at ~6 MBs between the two machines. I don't understand why the news isn't flying in. Does anyone have any ideas ? regards damian -- * Damian Hamill M.D. damian@cablenet.net * CableNet & The Landscape Channel * http://www.cablenet.net/ http://www.landscapetv.com/ From owner-freebsd-isp Fri Dec 5 06:28:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA29834 for isp-outgoing; Fri, 5 Dec 1997 06:28:26 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from ns3.harborcom.net (root@ns3.harborcom.net [206.158.4.7]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA29829 for ; Fri, 5 Dec 1997 06:28:22 -0800 (PST) (envelope-from bradley@harborcom.net) Received: from bradley by ns3.harborcom.net with smtp (Exim 1.73 #1) id 0xdyjl-0003kq-00; Fri, 5 Dec 1997 09:28:13 -0500 Date: Fri, 5 Dec 1997 09:28:13 -0500 (EST) From: Bradley Dunn X-Sender: bradley@ns3.harborcom.net To: Gaetan Feige cc: freebsd-isp@freebsd.org Subject: Re: User security In-Reply-To: <3.0.32.19971205083748.00ae0640@vsg.mobistar.be> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Dec 1997, Gaetan Feige wrote: > I am wondering what is the best way to give a user access to email on a bsd > box and block him from anything else like telnet, ftp into his account... Don't run telnetd, ftpd, etc. :) Seriously, black box mail servers that only allow access via IMAP or POP are the way to go if you can. You can use SSH for remote administration, and with SSH's "AllowUsers" configuration option you can specify exactly who can connect via SSH. Bradley From owner-freebsd-isp Fri Dec 5 06:55:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA01943 for isp-outgoing; Fri, 5 Dec 1997 06:55:39 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from hoima (hoima.i-way.co.uk [194.129.192.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA01929 for ; Fri, 5 Dec 1997 06:55:35 -0800 (PST) (envelope-from scot@duff-beer.com) Received: from homer.duff-beer.com by hoima via SMTP (951211.SGI.8.6.12.PATCH1502/951211.SGI) id OAA16398; Fri, 5 Dec 1997 14:54:40 GMT Date: Fri, 5 Dec 1997 14:55:07 +0000 (GMT) From: Scot Elliott To: Bradley Dunn cc: Gaetan Feige , freebsd-isp@FreeBSD.ORG Subject: Re: User security In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Try giving the user an invalid shell (like /nonexistant or a valid one like /bin/false). On Fri, 5 Dec 1997, Bradley Dunn wrote: > On Fri, 5 Dec 1997, Gaetan Feige wrote: > > > I am wondering what is the best way to give a user access to email on a bsd > > box and block him from anything else like telnet, ftp into his account... > > Don't run telnetd, ftpd, etc. :) > > Seriously, black box mail servers that only allow access via IMAP or POP > are the way to go if you can. You can use SSH for remote administration, > and with SSH's "AllowUsers" configuration option you can specify exactly > who can connect via SSH. > > Bradley > > ----------------------------------------------------------------------------- Scot Elliott (scot@poptart.org) | Work: +44 (0)1344 899401 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 ----------------------------------------------------------------------------- Public key available by finger at: finger scot@poptart.org or at: http://www.poptart.org/pgpkey.html From owner-freebsd-isp Fri Dec 5 07:45:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA07091 for isp-outgoing; Fri, 5 Dec 1997 07:45:09 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA07080 for ; Fri, 5 Dec 1997 07:45:05 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA26054; Fri, 5 Dec 1997 08:44:53 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA01108; Fri, 5 Dec 1997 08:44:51 -0700 Date: Fri, 5 Dec 1997 08:44:51 -0700 Message-Id: <199712051544.IAA01108@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bradley Dunn Cc: Gaetan Feige , freebsd-isp@FreeBSD.ORG Subject: Re: User security In-Reply-To: References: <3.0.32.19971205083748.00ae0640@vsg.mobistar.be> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Seriously, black box mail servers that only allow access via IMAP or POP > are the way to go if you can. You can use SSH for remote administration, > and with SSH's "AllowUsers" configuration option you can specify exactly > who can connect via SSH. There's one possible problem with SSH in that it allows remote users to 'forward' ports from the black-box machine to other machines unless you explicitly compile out the code. This is rather nasty if you allow people inside your firewall to the black-box machine, since they can forward out to other internal (unprotected) machines in your domain and wreak havoc. (No, this didn't happen, but it could have. :) Nate From owner-freebsd-isp Fri Dec 5 08:54:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA12951 for isp-outgoing; Fri, 5 Dec 1997 08:54:32 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from obiwan.TerraNova.net (root@obiwan.TerraNova.net [209.4.59.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA12943 for ; Fri, 5 Dec 1997 08:54:27 -0800 (PST) (envelope-from bofh@terranova.net) Received: from P1mpBSD.TerraNova.net (tog@guenhwyvar.TerraNova.net [209.4.59.4]) by obiwan.TerraNova.net (8.8.8/TerraNovaNet) with SMTP id LAA25520; Fri, 5 Dec 1997 11:57:41 -0500 (EST) Message-ID: <34883252.6119@terranova.net> Date: Fri, 05 Dec 1997 11:56:50 -0500 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 3.03 (Win95; I) MIME-Version: 1.0 To: freebsd-isp@FreeBSD.ORG CC: postmaster@ocracoke.net Subject: Re: Complimentary 3 day 2 night stay on the Outer Banks... References: <199712043400YAA35290@sample.kryan.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Barrier Island Realty wrote: I sent this to iosys.net and the originating dialup provider, (and place that's hosting this domain) ocracoke.net. I received no response from either. Time to add someone to the blacklist? I mean once is bad enough but twice? Although I can only assume iosys is being used as an innocent relay, ocracoke's site hints at offering "Interactive emailing service" And if they spam mailing lists like this how can ocracoke not have already gotten numerous complaints? -T -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- "Acceptance without proof is the fundamental characteristic of Western religion, Rejection without proof is the fundamental characteristic of Western science." -- Gary Zukav, "The Dancing Wu Li Masters" From owner-freebsd-isp Fri Dec 5 09:14:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA14614 for isp-outgoing; Fri, 5 Dec 1997 09:14:05 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from axe.cablenet.net (axe.cablenet.net [194.154.36.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA14609 for ; Fri, 5 Dec 1997 09:14:02 -0800 (PST) (envelope-from damian@axe.cablenet.net) Received: from axe (localhost [127.0.0.1]) by axe.cablenet.net (8.8.7/8.6.9) with SMTP id RAA11828; Fri, 5 Dec 1997 17:08:57 GMT Message-ID: <34883528.42877E5C@cablenet.net> Date: Fri, 05 Dec 1997 17:08:56 +0000 From: Damian Hamill Organization: CableNet Ltd X-Mailer: Mozilla 3.0 (X11; I; SunOS 4.1.4 sun4m) MIME-Version: 1.0 To: dg@root.com CC: freebsd-isp@freebsd.org Subject: Re: slow news server References: <199712051646.IAA04295@implode.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman wrote: > > >I have a news reader machine that is unable to keep up with the a > >single incoming feed. The feeder machine is running diablo and a large > > Make sure that you regularly (hourly) delete the articles in the > control.cancel newsgroup. If you don't it will grow extremely large and > the system will spend all of it's time trying to deal with it. I just found out a short while ago that that is exactly what the problem was. The control.cancel group had 384000 entries in it's directory. The directory itself was > 8 MB and an rm -rf to remove it has been running now for more than 90 minutes. I renamed the directory and the througput instantly went up to 300 articles a minute. Some other people have suggested I lower the interleave factor on the ccd array. I took the advice of the ccd man page and set the interleave factor to 65536, however someone else has suggested using 1024. Any thoughts either way ? Thanks for your help anyway. regards damian -- * Damian Hamill M.D. damian@cablenet.net * CableNet & The Landscape Channel * http://www.cablenet.net/ http://www.landscapetv.com/ From owner-freebsd-isp Fri Dec 5 09:20:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA15514 for isp-outgoing; Fri, 5 Dec 1997 09:20:46 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA15495 for ; Fri, 5 Dec 1997 09:20:41 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id JAA04587; Fri, 5 Dec 1997 09:23:28 -0800 (PST) Message-Id: <199712051723.JAA04587@implode.root.com> To: Damian Hamill cc: freebsd-isp@freebsd.org Subject: Re: slow news server In-reply-to: Your message of "Fri, 05 Dec 1997 17:08:56 GMT." <34883528.42877E5C@cablenet.net> From: David Greenman Reply-To: dg@root.com Date: Fri, 05 Dec 1997 09:23:28 -0800 Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Make sure that you regularly (hourly) delete the articles in the >> control.cancel newsgroup. If you don't it will grow extremely large and >> the system will spend all of it's time trying to deal with it. > >I just found out a short while ago that that is exactly what the >problem was. The control.cancel group had 384000 entries in it's >directory. The directory itself was > 8 MB and an rm -rf to remove >it has been running now for more than 90 minutes. I renamed the >directory and the througput instantly went up to 300 articles a minute. > >Some other people have suggested I lower the interleave factor on the >ccd array. I took the advice of the ccd man page and set the interleave >factor to 65536, however someone else has suggested using 1024. Any >thoughts either way ? 65536 should provide the best performance. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-isp Fri Dec 5 09:51:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA18860 for isp-outgoing; Fri, 5 Dec 1997 09:51:06 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from shell6.ba.best.com (jkb@shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA18854 for ; Fri, 5 Dec 1997 09:51:03 -0800 (PST) (envelope-from jkb@best.com) Received: from localhost (jkb@localhost) by shell6.ba.best.com (8.8.8/8.7.3) with SMTP id JAA28632; Fri, 5 Dec 1997 09:50:59 -0800 (PST) X-Authentication-Warning: shell6.ba.best.com: jkb owned process doing -bs Date: Fri, 5 Dec 1997 09:50:59 -0800 (PST) From: Jan Koum X-Sender: jkb@shell6.ba.best.com To: Travis Mikalson cc: freebsd-isp@freebsd.org Subject: Re: Complimentary 3 day 2 night stay on the Outer Banks... In-Reply-To: <34883252.6119@terranova.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Give them a call. Its an 800 number. I did and they said that many other people called. Gee I wonder why? Maybe because spamming is bad? :) -- Yan On Fri, 5 Dec 1997, Travis Mikalson wrote: >Barrier Island Realty wrote: > > >I sent this to iosys.net and the originating dialup provider, (and place >that's hosting this domain) ocracoke.net. > >I received no response from either. >Time to add someone to the blacklist? > >I mean once is bad enough but twice? > >Although I can only assume iosys is being used as an innocent relay, >ocracoke's site hints at offering "Interactive emailing service" > >And if they spam mailing lists like this how can ocracoke not have >already gotten numerous complaints? > >-T >-- >TerraNovaNet Internet Services - Key Largo, FL >Voice: (305)453-4011 Fax: (305)451-5991 >http://www.terranova.net/ >---------------------------------------------- >"Acceptance without proof is the fundamental characteristic of Western >religion, Rejection without proof is the fundamental characteristic of >Western science." > -- Gary Zukav, "The Dancing Wu Li Masters" > From owner-freebsd-isp Fri Dec 5 11:01:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25442 for isp-outgoing; Fri, 5 Dec 1997 11:01:30 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from inspace.net (nova.ispace.com [207.204.40.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA25419; Fri, 5 Dec 1997 11:01:22 -0800 (PST) (envelope-from gme@inspace.net) Received: from caffeine (caffeine.inspace.net [207.204.40.248]) by inspace.net (8.8.6) (8.8.6) (SPAM Stopper: 3.0b2) with SMTP id OAA06211; Fri, 5 Dec 1997 14:01:10 -0500 (EST) Received: by localhost with Microsoft MAPI; Fri, 5 Dec 1997 13:59:46 -0500 Message-ID: <01BD0186.0B94F9C0.gme@inspace.net> From: "George M. Ellenburg" To: "'isp@freebsd.org'" , "'hackers@freebsd.org'" Subject: FW: Touching Base Date: Fri, 5 Dec 1997 13:59:39 -0500 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, Gentlemen. An associate of mine is experiencing a rather unique problem with his FreeBSD box (P233, 64Mb Ram, 2 Maxtor 3.0gb IDE Hard Drives) ... I'm enclosing an excerpt from our message. Perhaps you may have some clues as I'm stumped. Regards, George Ellenburg -----Original Message----- From: Tom Holderby Sent: Friday, December 05, 1997 11:57 AM To: George M. Ellenburg Subject: Re: Touching Base George, [My Comments:] [...Non Relevant Material Cut...] Let me also give you a quick update on the FreeBSD situation. When I run that "tar x" while sitting at the console I see "Memory Parity Error". But I ran several iterations of the CheckIt memory diagnostic with its most advanced testing options and it's not turning up any errors, so I tend to believe it's a software problem. I have definitely seen software bugs cause memory parity halts, but that was mostly back in the days of assembler code under DOS when you tried to access a non existant add ress. I've never seen it under Unix before. Any ideas? Tom From owner-freebsd-isp Fri Dec 5 11:09:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA26233 for isp-outgoing; Fri, 5 Dec 1997 11:09:06 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from cbgw1.lucent.com (cbgw1.lucent.com [207.24.196.51]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA26227 for ; Fri, 5 Dec 1997 11:09:04 -0800 (PST) (envelope-from jdm@cbemg.cb.lucent.com) From: jdm@cbemg.cb.lucent.com Received: from cbemg.cb.lucent.com by cbig1.firewall.lucent.com (SMI-8.6/EMS-L sol2) id NAA07461; Fri, 5 Dec 1997 13:59:00 -0500 Received: by cbemg.cb.lucent.com (4.1/EMS-L gis) id AA15295; Fri, 5 Dec 97 14:13:01 EST Message-Id: <9712051413.ZM15292@cbemg> Date: Fri, 5 Dec 1997 14:13:00 -0500 X-Mailer: Z-Mail (3.2.1 31aug95) To: freebsd-isp@freebsd.org Subject: 56k modems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What equipment do I need on my end to use the 56k modems? As I understand it, a digital line is required so that must mean a channelized T1 and some sort of channel bank to demultiplex the line. Any help or pointers are appreciated. Thanks, Dale McSwain From owner-freebsd-isp Fri Dec 5 11:47:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA00265 for isp-outgoing; Fri, 5 Dec 1997 11:47:49 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA00239; Fri, 5 Dec 1997 11:47:26 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id OAA06038; Fri, 5 Dec 1997 14:44:10 -0500 (EST) X-Authentication-Warning: picnic.mat.net: chuckr owned process doing -bs Date: Fri, 5 Dec 1997 14:44:09 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: "George M. Ellenburg" cc: "'isp@freebsd.org'" , "'hackers@freebsd.org'" Subject: Re: FW: Touching Base In-Reply-To: <01BD0186.0B94F9C0.gme@inspace.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Dec 1997, George M. Ellenburg wrote: > Greetings, Gentlemen. > > An associate of mine is experiencing a rather unique problem with his > FreeBSD box (P233, 64Mb Ram, 2 Maxtor 3.0gb IDE Hard Drives) ... I'm > enclosing an excerpt from our message. Perhaps you may have some clues > as I'm stumped. > > Regards, > > George Ellenburg > > > -----Original Message----- > From: Tom Holderby > Sent: Friday, December 05, 1997 11:57 AM > To: George M. Ellenburg > Subject: Re: Touching Base > > George, > > [My Comments:] [...Non Relevant Material Cut...] > > Let me also give you a quick update on the FreeBSD situation. When I > run > that "tar x" while sitting at the console I see "Memory Parity Error". > But > I ran several iterations of the CheckIt memory diagnostic with its most > advanced testing options and it's not turning up any errors, so I tend > to > believe it's a software problem. I have definitely seen software bugs > cause memory parity halts, but that was mostly back in the days of > assembler code under DOS when you tried to access a non existant add > ress. > I've never seen it under Unix before. Any ideas? First, questions like this belong on the FreeBSD-Questions list, not hackers. Anyhow, it's not possible to test memory using a PC. The only way to do it is with an expensive piece of test equipment. The return from Checkit is only good for complete failures; any other indication isn't worth anything at all. I mean that -- checkit is worthless to catch anything but gross memory errors. FreeBSD (or really any other unix) works a PC's memory far harder than any DOS or Windows based application, so the chances really are that your friend has a memory problem. What he has to do is take it back to his vendor and really insist on new memory. There isn't any software problem like he's talking about. This kind of thing is seen quite a bit among folks new to Unix ... I'm not guessing here, your friend's complaint is common, and if he wants to run FreeBSD, he's going to have to get the problem fixed. Under Windows 95, heck, it reboots of it's own accord so often, you don't realize that some percentage of those reboots are hardware faults. Many users of FreeBSD have uptime (on busy internet servers) measured in _years_. > > Tom > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-isp Fri Dec 5 11:51:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA00664 for isp-outgoing; Fri, 5 Dec 1997 11:51:38 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from buffnet4.buffnet.net (buffnet4.buffnet.net [205.246.19.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA00647 for ; Fri, 5 Dec 1997 11:50:57 -0800 (PST) (envelope-from shovey@buffnet.net) Received: from buffnet11.buffnet.net (buffnet11.buffnet.net [205.246.19.55]) by buffnet4.buffnet.net (8.7.5/8.7.3) with SMTP id OAA25020; Fri, 5 Dec 1997 14:49:43 -0500 (EST) Date: Fri, 5 Dec 1997 14:49:43 -0500 (EST) From: Steve Hovey To: jdm@cbemg.cb.lucent.com cc: freebsd-isp@freebsd.org Subject: Re: 56k modems In-Reply-To: <9712051413.ZM15292@cbemg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Dec 1997 jdm@cbemg.cb.lucent.com wrote: > > What equipment do I need on my end to use > the 56k modems? As I understand it, a digital > line is required so that must mean a channelized > T1 and some sort of channel bank to demultiplex > the line. Any help or pointers are appreciated. You need a term server that can take the T1s (channelized or PRI - the channelized MUST be trunk side) and supports one or both of the protocols. We use the USR total control exterprise hubs for X2, and ascend 4048's for Flex - While there are other factors involved, Im told our flex functions better than the flex of one of our competitors that uses an upgraded lexington portmaster - but I have no personal objective proof of this. Both of these are capable of using the same radius server (We use the merit one) which cuts down on computer guy burnout! :) And both can be set to use a secondary radius server should its primary be too busy to respond. If you go with a flex machine - make certain its flashed to the current code - and say the same to any users who have trouble keeping a connection. Our ascends came with beta ware and were droppy till flashed to the current code. Both products are easy to flash. ------------------------------------------------------------------ Steve Hovey Chief Engineer BuffNET More Than Just a Connection! ------------------------------------------------------------------ From owner-freebsd-isp Fri Dec 5 12:51:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA07130 for isp-outgoing; Fri, 5 Dec 1997 12:51:04 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from kjsl.com (Limpia.KJSL.COM [198.137.202.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA07122 for ; Fri, 5 Dec 1997 12:51:01 -0800 (PST) (envelope-from javier@kjsl.com) Received: (from javier@localhost) by kjsl.com (8.8.5/8.8.5) id MAA19412; Fri, 5 Dec 1997 12:50:55 -0800 (PST) Date: Fri, 5 Dec 1997 12:50:55 -0800 (PST) Message-Id: <199712052050.MAA19412@kjsl.com> From: Javier Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: jdm@cbemg.cb.lucent.com Cc: freebsd-isp@freebsd.org Subject: 56k modems In-Reply-To: <9712051413.ZM15292@cbemg> References: <9712051413.ZM15292@cbemg> X-Mailer: VM 6.33 under Emacs 19.34.1 Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk jdm@cbemg.cb.lucent.com writes: > What equipment do I need on my end to use > the 56k modems? As I understand it, a digital > line is required so that must mean a channelized > T1 and some sort of channel bank to demultiplex > the line. Any help or pointers are appreciated. Channel banks usually end up with d/a conversions, which is what you must avoid in order to support 56K modems. Various router vendors have several products. I work at Cisco, the AS5200 and AS5300 both support 56K modems. Also, be aware that there are two competing standards at the moment, X2 pushed by USR/3Com (they're the same company now) and Kflex, pushed by Rockwell, et al. Cisco gear supports Kflex at the moment, though I believe just about every vendor out there stated they will support whatever standard becomes, well, standard early next year. -jav (not a Cisco spokesperson) From owner-freebsd-isp Fri Dec 5 13:11:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA09121 for isp-outgoing; Fri, 5 Dec 1997 13:11:22 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from kjsl.com (Limpia.KJSL.COM [198.137.202.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA09100; Fri, 5 Dec 1997 13:11:15 -0800 (PST) (envelope-from javier@kjsl.com) Received: (from javier@localhost) by kjsl.com (8.8.5/8.8.5) id NAA19475; Fri, 5 Dec 1997 13:11:08 -0800 (PST) Date: Fri, 5 Dec 1997 13:11:08 -0800 (PST) Message-Id: <199712052111.NAA19475@kjsl.com> From: Javier Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Didier Derny Cc: isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: HELP! In-Reply-To: References: X-Mailer: VM 6.33 under Emacs 19.34.1 Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Didier Derny writes: > - the router is a Cisco 1603 with 1 BRI S/T interface. > - IOS 11.2 > > - Phone number: 0561163290 > - Login: omnix > - Password: xxxxx > - Network: 194.149.170.24/29 (255.255.255.248) > - Routeur: 194.149.170.25 > - Default route: 194.149.170.1 > - Primary DNS: 194.149.160.9 > - Secondary DNS: 194.149.160.2 Before I come up with a sample config, can you tell me whether you'll be using unnumbered links for the BRI interface? Also, I will assume that the router's Ethernet interface on the router will be 194.149.170.25, correct? -jav From owner-freebsd-isp Fri Dec 5 14:50:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19527 for isp-outgoing; Fri, 5 Dec 1997 14:50:06 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from alabama.nwlink.com (mail.nwlink.com [209.20.130.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA19427 for ; Fri, 5 Dec 1997 14:49:14 -0800 (PST) (envelope-from bryn@nwlink.com) Received: from utah (bryn@nwlink.com [199.242.23.2]) by alabama.nwlink.com (8.8.8/8.8.8) with SMTP id OAA04671; Fri, 5 Dec 1997 14:48:09 -0800 (PST) Date: Fri, 5 Dec 1997 14:42:08 -0800 (PST) From: "Bryn Wm. Moslow" X-Sender: bryn@utah To: freebsd-isp@freebsd.org cc: jayk@nwlink.com Subject: Adaptec 2940/Seagate Failures Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, sorry that this is a bit windy but I'm desperate: I'm still having big problems with FreeBSD, the Adaptec 2940UW, and Seagate Drives. When the system gets heavily loaded (i.e. 65-75 sendmail processes, 20 or so poppers,) often it comes to a complete stop and sure enough I can get to the console and discover just about the same thing every time (which is at the bottom of this message along with my dmesg output for informational purposes.) I've tried FreeBSD's both 2.2.2 and 2.2.5, sendmail 8.8.5, 8.8.6, 8.8.7, 8.8.8, qpopper 2.3, 2.4. I would like to note that disk I/O was much smoother and system load was significantly lower with 2.2.5 but it was only two hours under load before it pooped the first time as opposed to a couple days under 2.2.2. In fact, it was odd because the load was 0.7 and iostat was about 3800sps on sd2 average when the most recent death (see 'the hell' below) occured. I've been reading the long debate about the 2940 and FreeBSD for some time and just today went through my whole archive of freebsd-isp and noted some things. What especially stands out is the number of people saying that they have no problem, "it works great," and then noting that they're not really using it or only have a tape attached, etc., literally in the same breath. The people who DO seem to be having problems are running the 2940 under heavy load conditions and having to power cycle servers at horrible times like myself. If you have an archive of freebsd-isp do a search on "Adaptec 2940" and you'll see what I'm talking about. Just an observation and opinion: I'm not trying to PO anyone but I think there has to be more attention paid to the stability of the SCSI subsystem, specifically under heavy loads. Once again: I love you all, I love Chuck, please help me ;). Notes: - I've used every combination of AHC_TAGENABLE, AHC_SCBPAGING_ENABLE, and AHC_ALLOW_MEMIO in the kernel possible and each one in cooperation with the others or on its own eventually brings down the system. - We've broken out the mail spool for local mail to a directory structure based on the first letters of username such as: /var/mail/u/us/username. This has helped overall but iostat still hits the roof when people get lots of mail (lists, spam) and pop3 is yanking down large mail files. - per advice from other FreeBSD users and non-FreeBSD users and an electrical engineer, the narrow drive on a separate controller from the wide drives. - The drives are all internal, the bus is terminated and the cable is only 0.5m. - The controller is in Ultra mode and I would like to keep it there if possible. I've tried it without to no avail anyway. I'm quite sure this should not be a problem as I have a BSDI 3.0 box running news that does at least ten times the I/O per day at a higher load on two Adaptec 2940's and 10 drives in Ultra mode with a 4-disk ccd (sp0 in BSDI) with the same CPU, but I want to believe in the power of FreeBSD. :) The hell: (This particular kernel was with AHC_SCBPAGING_ENABLE but I get similar results with the other options and ultimately a bus failure and/or lockup and/or panic. I don't have as much trouble with no extra ahc options but the system gets VERY s-l-o-w under load.) SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued \M^?\^OA Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): abort message in message buffer sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 sd2(ahc1:2:0): no longer in timeout ahc1: Issued Channel A Bus Reset. 4 SCBs aborted dmesg output: (No ahc kernel options) FreeBSD 2.2.2-RELEASE #0: Wed Nov 19 13:31:09 PST 1997 bryn@alabama.nwlink.com:/usr/src/sys/compile/ALABAMA CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff,MTRR,PGE,MCA,CMOV> real memory = 268435456 (262144K bytes) avail memory = 257245184 (251216K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:1:0 chip2 rev 0 on pci0:1:1 vx0 <3COM 3C905 Fast Etherlink XL PCI> rev 0 int a irq 12 on pci0:9 mii[*mii*] address 00:60:08:0a:42:32 ahc0 rev 0 int a irq 10 on pci0:10 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST52160N 0285" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2069MB (4238282 512 byte sectors) vga0 rev 0 on pci0:11 ahc1 rev 0 int a irq 11 on pci0:12 ahc1: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc1 waiting for scsi devices to settle (ahc1:1:0): "SEAGATE ST34572W 0718" type 0 fixed SCSI 2 sd1(ahc1:1:0): Direct-Access 4340MB (8888924 512 byte sectors) (ahc1:2:0): "SEAGATE ST34572W 0784" type 0 fixed SCSI 2 sd2(ahc1:2:0): Direct-Access 4340MB (8888924 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 flags 0x1 on motherboard npx0: INT 16 interface WARNING: / was not properly dismounted. Thanks for your time, Bryn From owner-freebsd-isp Fri Dec 5 15:39:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA23792 for isp-outgoing; Fri, 5 Dec 1997 15:39:51 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from hq.seicom.net (mail.seicom.net [194.97.200.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA23783 for ; Fri, 5 Dec 1997 15:39:45 -0800 (PST) (envelope-from udesign!lukas@hq.seicom.net) Received: from udesign.UUCP by hq.seicom.net (8.8.5/8.8.3) with UUCP id AAA08572; Sat, 6 Dec 1997 00:29:43 +0100 (CET) Received: by reactor.design.de id m0xe7Mm-000BijC (Debian Smail-3.2 1996-Jul-4 #2); Sat, 6 Dec 1997 00:41:04 +0100 (MET) Message-ID: <19971206004104.55821@reactor> Date: Sat, 6 Dec 1997 00:41:04 +0100 From: Lukas Wunner To: "Bryn Wm. Moslow" Cc: freebsd-isp@FreeBSD.ORG, jayk@nwlink.com Subject: Re: Adaptec 2940/Seagate Failures References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85 In-Reply-To: ; from Bryn Wm. Moslow on Fri, Dec 05, 1997 at 02:42:08PM -0800 Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > The people who DO seem to be having problems are running the 2940 > under heavy load conditions and having to power cycle servers at horrible > times like myself. I have two 2940's in my baby news.seicom.net, each with four disks attached to it. This is a 2.2.2 machine running under extremely heavy load (probably something like 30GB i/o per day would seem reasonable). All I can say is that it works like a charm. I usually get uptimes of up to 70 days. The only problems I have noticed are occasional error messages like > ahc1: WARNING no command for scb 6 (cmdcmplt) > QOUTCNT == 14 > ahc1: WARNING no command for scb 6 (cmdcmplt) > QOUTCNT == 13 > ahc1: WARNING no command for scb 6 (cmdcmplt) [...] > QOUTCNT == 2 > ahc1: WARNING no command for scb 6 (cmdcmplt) > QOUTCNT == 1 > ahc1: WARNING no command for scb 6 (cmdcmplt) > QOUTCNT == 1 As these seem to be harmless, I didn't try to find out what caused them. Lukas. -- lukas wunner unix, internetworking and security engineer lukas@wunner.de LW26-RIPE http://www.wunner.de/~lukas/ Funkmodems mit 2.4GHz FAQ http://www.wunner.de/~lukas/funk/ From owner-freebsd-isp Fri Dec 5 15:45:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA24205 for isp-outgoing; Fri, 5 Dec 1997 15:45:16 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from magicnet.magicnet.net (root@magicnet.magicnet.net [204.96.116.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA24177 for ; Fri, 5 Dec 1997 15:44:59 -0800 (PST) (envelope-from bill@bilver.magicnet.net) Received: from bilver.magicnet.net (root@localhost) by magicnet.magicnet.net (8.8.6/8.8.6) with UUCP id SAA18740 for freebsd-isp@freebsd.org; Fri, 5 Dec 1997 18:40:03 -0500 (EST) Received: (from bill@localhost) by bilver.magicnet.net (8.8.5/8.7.3) id SAA27330 for freebsd-isp@freebsd.org; Fri, 5 Dec 1997 18:16:07 -0500 (EST) From: Bill Vermillion Message-Id: <199712052316.SAA27330@bilver.magicnet.net> Subject: Re: FW: Touching Base In-Reply-To: from Chuck Robey at "Dec 5, 97 02:44:09 pm" To: freebsd-isp@freebsd.org Date: Fri, 5 Dec 1997 18:16:07 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Recently Chuck Robey said: > > -----Original Message----- > > From: Tom Holderby > > Sent: Friday, December 05, 1997 11:57 AM > > To: George M. Ellenburg > > Subject: Re: Touching Base > > > > George, > > > > [My Comments:] [...Non Relevant Material Cut...] > > > > Let me also give you a quick update on the FreeBSD situation. When I > > run > > that "tar x" while sitting at the console I see "Memory Parity Error". > > But > > I ran several iterations of the CheckIt memory diagnostic with its most > > advanced testing options and it's not turning up any errors, so I tend > > to > > believe it's a software problem. .... > Anyhow, it's not possible to test memory using a PC. The only > way to do it is with an expensive piece of test equipment. The return > from Checkit is only good for complete failures; any other indication > isn't worth anything at all. When I've been asked about checking memory in PC based machines, I tell them the best program to check memory is Unix. :-) I saw a memory test program from a board manufacturer that passed all the memory with flying colors, but would core dump in Unix. Looking at the core dump there were large areas of text, and about 1/2 the letters were of by one character. It acted like bit 0 (this first bit) was stuck on permanently. Pulled the board, and there in the first position of all the 256K chips (this was a while ago) there was a lonely 64K chip. Trust nothing. I remember from long ago that testing memory on a PC would take about 15 minutes for each 32K, complete with walking bits, checkerboard patterns, variable timing on refresh, etc. I've seen nothing like that. All of the PC memory checkers I've seen really seem only to tell you there's a chip in the socket, and as the above shows, it can't even tell if the chip is the wrong one. -- bill@bilver.magicnet.net | bill@bilver.com From owner-freebsd-isp Fri Dec 5 16:51:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29548 for isp-outgoing; Fri, 5 Dec 1997 16:51:52 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from mercury.jorsm.com (mercury.jorsm.com [207.112.128.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA29541 for ; Fri, 5 Dec 1997 16:51:49 -0800 (PST) (envelope-from jeff@mercury.jorsm.com) Received: from localhost (jeff@localhost) by mercury.jorsm.com (8.8.7/8.8.7) with SMTP id SAA01944; Fri, 5 Dec 1997 18:51:44 -0600 (CST) Date: Fri, 5 Dec 1997 18:51:44 -0600 (CST) From: Jeff Lynch To: "Bryn Wm. Moslow" cc: freebsd-isp@freebsd.org, jayk@nwlink.com Subject: Re: Adaptec 2940/Seagate Failures In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Dec 1997, Bryn Wm. Moslow wrote: > I've been reading the long debate about the 2940 and FreeBSD for some time > and just today went through my whole archive of freebsd-isp and noted some > things. What especially stands out is the number of people saying that > they have no problem, "it works great," and then noting that they're not > really using it or only have a tape attached, etc., literally in the same > breath. The people who DO seem to be having problems are running the 2940 > under heavy load conditions and having to power cycle servers at horrible > times like myself. If you have an archive of freebsd-isp do a search on > "Adaptec 2940" and you'll see what I'm talking about. Just an observation > and opinion: I'm not trying to PO anyone but I think there has to be more > attention paid to the stability of the SCSI subsystem, specifically under > heavy loads. Once again: I love you all, I love Chuck, please help me ;). > Possibly a flakey controller? I load mine pretty heavily. 60+ apache httpds, maybe 10 sendmails, and 10 or so poppers. Also 5 sambas 5 ftpds, and a handful of shells, including mine which always has a larger than normal mailbox loaded in pine. Using same ultra-wide drives, internal only (IBM oemed seagates) in ultra mode. ========================================================================= Jeffrey A. Lynch, President JORSM Internet email: jeff@jorsm.com Northwest Indiana's Full-Service Provider Voice: (219)322-2180 927 Sheffield Avenue, Dyer, IN 46311 Autoresponse: info@jorsm.com http://www.jorsm.com From owner-freebsd-isp Fri Dec 5 16:57:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29934 for isp-outgoing; Fri, 5 Dec 1997 16:57:08 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from dt051n19.san.rr.com (dt051n19.san.rr.com [204.210.32.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA29921 for ; Fri, 5 Dec 1997 16:57:02 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (localhost [127.0.0.1]) by dt051n19.san.rr.com (8.8.8/8.8.8) with ESMTP id QAA04362; Fri, 5 Dec 1997 16:56:41 -0800 (PST) (envelope-from Studded@dal.net) Message-ID: <3488A2C9.BBF2FD51@dal.net> Date: Fri, 05 Dec 1997 16:56:41 -0800 From: Studded X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: "Bryn Wm. Moslow" CC: freebsd-isp@freebsd.org Subject: Re: Adaptec 2940/Seagate Failures References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bryn Wm. Moslow wrote: > > Hello, sorry that this is a bit windy but I'm desperate: > > I'm still having big problems with FreeBSD, the Adaptec 2940UW, A friend of mine who I talked into using FreeBSD was having similar problems with his 2940 until he got the latest BIOS chip from Adaptec, and enabled SCAM support on the card. If you haven't taken these steps yet, I'd highly recommend giving it a shot and see how you do. Good luck, Doug From owner-freebsd-isp Fri Dec 5 17:03:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA00549 for isp-outgoing; Fri, 5 Dec 1997 17:03:51 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from obiwan.TerraNova.net (root@obiwan.TerraNova.net [209.4.59.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA00544 for ; Fri, 5 Dec 1997 17:03:48 -0800 (PST) (envelope-from bofh@terranova.net) Received: from P1mpBSD.TerraNova.net (tog@guenhwyvar.TerraNova.net [209.4.59.4]) by obiwan.TerraNova.net (8.8.8/TerraNovaNet) with SMTP id UAA08224; Fri, 5 Dec 1997 20:07:13 -0500 (EST) Message-ID: <3488A507.65CB@terranova.net> Date: Fri, 05 Dec 1997 20:06:15 -0500 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 3.03 (Win95; I) MIME-Version: 1.0 To: "Bryn Wm. Moslow" CC: freebsd-isp@freebsd.org, jayk@nwlink.com Subject: Re: Adaptec 2940/Seagate Failures References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bryn Wm. Moslow wrote: > - I've used every combination of AHC_TAGENABLE, AHC_SCBPAGING_ENABLE, and > AHC_ALLOW_MEMIO in the kernel possible and each one in cooperation with > the others or on its own eventually brings down the system. Ok, for the record, I'm using all of these options together as well. AHC_SCBPAGING_ENABLE AHC_TAGENABLE AHC_ALLOW_MEMIO > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted Wow! I'm quite familiar with this unfortunately. I've been getting this occasionally on my lightly-loaded server with an AHA-2940UW and two Micropolis drives: ahc0 rev 0 int a irq 11 on pci0:14 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "MICROP 3243-19 1128RFAV RFAV" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4095MB (8388315 512 byte sectors) ahc0: target 2 Tagged Queuing Device (ahc0:2:0): "MICROP 3243-19 1128RFAV RFAV" type 0 fixed SCSI 2 sd1(ahc0:2:0): Direct-Access 4095MB (8388315 512 byte sectors) Your hell looks just like mine. Mine has only been fatal once. I've always attributed it to the HD (and backup very frequently) since it's always the same one.. but then again that is the drive that does the most I/O. The last failing HD I dealt with always req'd a cold boot to get running again.. I just had it happen a couple days ago as a matter of fact.. it wasn't fatal at all, just a hiccup; I was working on the system at the time. sd1(ahc0:2:0): SCB 0x6 - timed out in command phase, SCSISIGI == 0x84 SEQADDR = 0x4e SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 Ordered Tag queued sd1(ahc0:2:0): SCB 0x7 timedout while recovery in progress sd0(ahc0:0:0): SCB 0x0 timedout while recovery in progress sd1(ahc0:2:0): SCB 0x2 timedout while recovery in progress Ordered Tag sent sd0(ahc0:0:0): SCB 0x3 timedout while recovery in progress sd0(ahc0:0:0): SCB 0x1 timedout while recovery in progress sd1(ahc0:2:0): SCB 0x6 - timed out in command phase, SCSISIGI == 0x84 SEQADDR = 0x4e SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 sd1(ahc0:2:0): abort message in message buffer sd1(ahc0:2:0): SCB 6 - Abort Tag Completed. sd1(ahc0:2:0): no longer in timeout sd1(ahc0:2:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Ordered Tag queued sd1(ahc0:2:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1(ahc0:2:0): Queueing an Abort SCB sd1(ahc0:2:0): Abort Message Sent sd1(ahc0:2:0): SCB 7 - Abort Tag Completed. sd1(ahc0:2:0): no longer in timeout Ordered Tag sent There did happen to be a higher than normal load on the system at the time. I've changed the cable thrice and the heat seems well within acceptable parameters. So anyway I guess this is a me too. I think I started having this problem around 2.2.1. I'm currently running: FreeBSD obiwan.TerraNova.net 2.2.5-STABLE FreeBSD 2.2.5-STABLE #0: Mon Nov 24 05:16:33 EST 1997 mikaltra@obiwan.TerraNova.net:/usr/src/sys/compile/obiwan i386 I've been taught to question the hardware first, the OS later so I've never mentioned it as I don't have replacement drives to try so there still remains a variable (oh I tried another 2940UW, too) Later, -T -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- "Acceptance without proof is the fundamental characteristic of Western religion, Rejection without proof is the fundamental characteristic of Western science." -- Gary Zukav, "The Dancing Wu Li Masters" From owner-freebsd-isp Fri Dec 5 18:31:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA07250 for isp-outgoing; Fri, 5 Dec 1997 18:31:54 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA07241 for ; Fri, 5 Dec 1997 18:31:51 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id SAA16745; Fri, 5 Dec 1997 18:31:56 -0800 (PST) To: "George M. Ellenburg" cc: "'isp@freebsd.org'" Subject: Re: FW: Touching Base In-reply-to: Your message of "Fri, 05 Dec 1997 13:59:39 EST." <01BD0186.0B94F9C0.gme@inspace.net> Date: Fri, 05 Dec 1997 18:31:55 -0800 Message-ID: <16742.881375515@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Redirected to just -isp; please don't cross-post to more than one mailing list - thanks!] > An associate of mine is experiencing a rather unique problem with his > FreeBSD box (P233, 64Mb Ram, 2 Maxtor 3.0gb IDE Hard Drives) ... I'm > enclosing an excerpt from our message. Perhaps you may have some clues > as I'm stumped. Not unique at all, this is bad memory, not a software problem. The fact that CheckIt did not find any errors is also hardly surprising. CheckIt is not a sufficient tool for this purpose and will find only the most egregiously obvious errors (and even then, almost never at all if your guy forgot to turn the internal and external caches off before running the CheckIt tests!) - any hardware engineer who actually knows what he is doing will laugh at this particular diagnostic method, and with good reason. I've talked with TouchStone software, the makers of this beast, and when challenged they'll admit that a hardware based memory checker is really the only tool for the job if you want to be sure. I've taken *known bad* SIMMS and run CheckIt on them, just as a test, and had it pass them with flying colors (at which point I called TouchStone and had the aformentioned dialog, just to be sure my suspicions were correct). Jordan > > Regards, > > George Ellenburg > > > -----Original Message----- > From: Tom Holderby > Sent: Friday, December 05, 1997 11:57 AM > To: George M. Ellenburg > Subject: Re: Touching Base > > George, > > [My Comments:] [...Non Relevant Material Cut...] > > Let me also give you a quick update on the FreeBSD situation. When I > run > that "tar x" while sitting at the console I see "Memory Parity Error". > But > I ran several iterations of the CheckIt memory diagnostic with its most > advanced testing options and it's not turning up any errors, so I tend > to > believe it's a software problem. I have definitely seen software bugs > cause memory parity halts, but that was mostly back in the days of > assembler code under DOS when you tried to access a non existant add > ress. > I've never seen it under Unix before. Any ideas? > > Tom > From owner-freebsd-isp Fri Dec 5 19:20:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10466 for isp-outgoing; Fri, 5 Dec 1997 19:20:48 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from word.smith.net.au (ppp8.portal.net.au [202.12.71.108]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10437; Fri, 5 Dec 1997 19:20:38 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA01340; Sat, 6 Dec 1997 13:45:15 +1030 (CST) Message-Id: <199712060315.NAA01340@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Chuck Robey cc: "George M. Ellenburg" , "'isp@freebsd.org'" , "'hackers@freebsd.org'" Subject: Re: FW: Touching Base In-reply-to: Your message of "Fri, 05 Dec 1997 14:44:09 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Dec 1997 13:45:15 +1030 From: Mike Smith Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Let me also give you a quick update on the FreeBSD situation. When I > > run > > that "tar x" while sitting at the console I see "Memory Parity Error". > > But > > I ran several iterations of the CheckIt memory diagnostic with its most > > advanced testing options and it's not turning up any errors, so I tend > > to > > believe it's a software problem. I have definitely seen software bugs ... > hackers. Anyhow, it's not possible to test memory using a PC. The only > way to do it is with an expensive piece of test equipment. The return > from Checkit is only good for complete failures; any other indication > isn't worth anything at all. > > I mean that -- checkit is worthless to catch anything but gross memory > errors. Just to add emphasis to this particular point; the CheckIt manual goes to some considerable pains to make the above *very*clear*. Test and diagnostic software is fine as far as it goes, but too many people are willing to believe that if something says everything is alright, it must be so. Hello Peter Norton, McAfee, etc. etc. etc. mike From owner-freebsd-isp Fri Dec 5 22:51:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA25038 for isp-outgoing; Fri, 5 Dec 1997 22:51:29 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from uranus.intrastar.net (jsuter@uranus.intrastar.net [206.136.25.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA25033 for ; Fri, 5 Dec 1997 22:51:26 -0800 (PST) (envelope-from jsuter@uranus.intrastar.net) Received: from localhost (jsuter@localhost) by uranus.intrastar.net (8.8.7/8.8.7) with SMTP id BAA02440 for ; Sat, 6 Dec 1997 01:51:38 GMT (envelope-from jsuter@uranus.intrastar.net) Date: Sat, 6 Dec 1997 01:51:37 +0000 (GMT) From: Jacob Suter To: freebsd-isp@freebsd.org Subject: Portslave? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone checked out portslave? It compiled fine in a test Slackware box, but it doesn't seem to want to work in FreeBSD. My C skills are nearly nonexistant when it comes to porting stuff from Linux to FreeBSD... The website is http://homepage.cistron.nl/~miquels/radius/.... They also have a radius server and some other goodies on there (for the record the radius server works fine in FreeBSD, go figure). Portslave is actually a PM2 emulator for Unix (linux apparently). Appears to work nicely but I really don't want to think about running anything that might actually need to be used on a regular basis under Linux. Thanks Jacob Suter Intrastellar Internet Service From owner-freebsd-isp Sat Dec 6 02:17:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA06068 for isp-outgoing; Sat, 6 Dec 1997 02:17:23 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from arnica.datanet.hu (arnica.datanet.hu [194.149.0.147]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA06050 for ; Sat, 6 Dec 1997 02:17:16 -0800 (PST) (envelope-from agdolla@arnica.datanet.hu) Received: from localhost (agdolla@localhost) by arnica.datanet.hu (8.8.5/8.8.5) with SMTP id LAA24519; Sat, 6 Dec 1997 11:15:48 +0100 Date: Sat, 6 Dec 1997 11:15:48 +0100 (NFT) From: Gabor Dolla To: "Bryn Wm. Moslow" cc: freebsd-isp@FreeBSD.ORG, jayk@nwlink.com Subject: Re: Adaptec 2940/Seagate Failures In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > things. What especially stands out is the number of people saying that > they have no problem, "it works great," and then noting that they're not > really using it or only have a tape attached, etc., literally in the same > breath. The people who DO seem to be having problems are running the 2940 > - I've used every combination of AHC_TAGENABLE, AHC_SCBPAGING_ENABLE, and > AHC_ALLOW_MEMIO in the kernel possible and each one in cooperation with > the others or on its own eventually brings down the system. > Hi We had problems when we tried to use FreeBSD as a news server, it always went down with similar problems you have. The funny things is that we have now a Pentium running FreeBSD 2.2.5 and squid with 128M RAM and a wide 2940 scsi controller and it never goes down! I even compiled a new kernel with all AHC_... options and still it is very stable. It was the same with 2.2.2. It does have a nice load as hundreds of users use this host as a proxy server plus it works with other squids remote as well. Both innd and squid is I/O intensive and uses lots of small files... Next week we try to use FreeBSD as a news server again but with DNEWS this time :) Also, I installed a new disk into the proxy server and during boot it says somethins like 'sending SDTR' when the controller negotiates with this new disk. What does that mean ? best Gabor Dolla DataNet Ltd, Budapest, Hungary From owner-freebsd-isp Sat Dec 6 03:25:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA08886 for isp-outgoing; Sat, 6 Dec 1997 03:25:28 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA08880 for ; Sat, 6 Dec 1997 03:25:19 -0800 (PST) (envelope-from itfs!news!nnd%itfs.nsk.su@gw.itfs.nsk.su) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id RAA17081 for isp@freebsd.org; Sat, 6 Dec 1997 17:25:10 +0600 Received: by itfs.nsk.su; Sat, 6 Dec 97 17:23:52 +0600 (NSK) Received: (from daemon@localhost) by news.itfs.nsk.su (8.7.5/8.6.12) id RAA19696; Sat, 6 Dec 1997 17:11:32 +0600 (NSK) From: nnd@itfs.nsk.su To: isp@freebsd.org Subject: Re: Portslave? Date: 6 Dec 1997 11:11:30 GMT Message-ID: <66bbt2$ive@news.itfs.nsk.su> References: Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jacob Suter wrote: > Has anyone checked out portslave? It compiled fine in a test Slackware > box, but it doesn't seem to want to work in FreeBSD. My C skills are > nearly nonexistant when it comes to porting stuff from Linux to FreeBSD... I use portslave-1.15 on my FreeBSD-3.0-based RAS . To make it works on FreeBSD I must throw out some parts of it - f.e. working with modems in an UNIX-traditional way - setting AA and waiting for CD, permitting of "local" logins through '!name', writing local utmp/wtmp records. I must also though away contained in portslave sources 'syslog.c'. And I'm also dont't use 'ppp-2.2.0f-radius' from portslave-1.15 but rather applay corresponding patches to FreeBSD-3.0's pppd directly. Now I am working (thinking ?) on the new simplified version of the program that will work with/after 'getty'. FreeBSD's 'getty' can talk to modems and other kind of serial links very successfully (and even understand and autodetect PPP) so my new program must only understand some type of configuration file setting RAS's ports parameters and can talk to RADIUS server to obtain user authentication and PPP-parameters. Other part of the RAS functionality must be put in pppd (or ppp) - obtaining autentication and PPP parameters for AutoPPP case and accounting through RADIUS server. N.Dudorov From owner-freebsd-isp Sat Dec 6 04:32:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA14344 for isp-outgoing; Sat, 6 Dec 1997 04:32:35 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from spooky.eis.net.au (spooky.eis.net.au [203.12.171.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA14333 for ; Sat, 6 Dec 1997 04:32:25 -0800 (PST) (envelope-from ernie@spooky.eis.net.au) Received: (from ernie@localhost) by spooky.eis.net.au (8.8.7/8.8.3) id WAA19154; Sat, 6 Dec 1997 22:31:59 +1000 (EST) From: Ernie Elu Message-Id: <199712061231.WAA19154@spooky.eis.net.au> Subject: Re: Adaptec 2940/Seagate Failures In-Reply-To: from "Gabor Dolla" at "Dec 6, 97 11:15:48 am" X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: agdolla@telnet.datanet.hu (Gabor Dolla) Date: Sat, 6 Dec 1997 22:31:50 +1000 (EST) Cc: freebsd-isp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] Content-Type: text Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > things. What especially stands out is the number of people saying that > > they have no problem, "it works great," and then noting that they're not > > really using it or only have a tape attached, etc., literally in the same > > breath. The people who DO seem to be having problems are running the 2940 > > > - I've used every combination of AHC_TAGENABLE, AHC_SCBPAGING_ENABLE, and > > AHC_ALLOW_MEMIO in the kernel possible and each one in cooperation with > > the others or on its own eventually brings down the system. > > > Hi > > We had problems when we tried to use FreeBSD as a news server, it always > went down with similar problems you have. > > The funny things is that we have now a Pentium running FreeBSD 2.2.5 and > squid with 128M RAM and a wide 2940 scsi controller and it never goes > down! I even compiled a new kernel with all AHC_... options and still it > is very stable. It was the same with 2.2.2. It does have a nice load as > hundreds of users use this host as a proxy server plus it works with other > squids remote as well. > > Both innd and squid is I/O intensive and uses lots of small files... > > Next week we try to use FreeBSD as a news server again but with DNEWS this > time :) > > Also, I installed a new disk into the proxy server and during boot it says > somethins like 'sending SDTR' when the controller negotiates with this new > disk. What does that mean ? > > best > > Gabor Dolla > DataNet Ltd, Budapest, Hungary > > > I don't know if this is related but I have had a spate of SCSI bus errors on my proxy server, I run Quanutm Fireball 4.3GB drives of which I have bought 5 over the last 3 months. I am running a generic NCR 53c810 based controller but I have also had the same failures with an Adaptec 1542 controller. The first 2 drives I bought are running fine, the next 3 all gave intermittent scsi bus errors that required rebooting the server. I was running FreeBSD 2.2.2 and in an attempt to isolate the problem I replaced ALL the hadware twice and even did a fresh install/upgrade to 2.2.5. No luck, in desparation I sent back 3 of the drives and replaced them with a Segate Barracuda 9.1GB drive which had not failed in the past week. The point I am trying to make is that something was very marginal to bring out a batch fault in the Quantum drives that since have run fine under MacOS or Windows 95/NT. Unfortunately I have an ISP job to get on with so I could not put in the time to zero in any closer to the problem. A SCSI intermittent is very hard to find. - Ernie. From owner-freebsd-isp Sat Dec 6 05:11:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA16479 for isp-outgoing; Sat, 6 Dec 1997 05:11:41 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from mail.primelink.com (mail.primelink.com [206.24.58.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA16461 for ; Sat, 6 Dec 1997 05:11:32 -0800 (PST) (envelope-from kbrown@primelink.com) Received: from hack ([206.24.58.11]) by mail.primelink.com (post.office MTA v1.9.3 ID# 0-11777) with SMTP id AAA126 for ; Sat, 6 Dec 1997 07:18:36 -0600 Message-Id: <3.0.32.19971206071033.00920df0@mail.primelink.com> X-Sender: darkstar@mail.primelink.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 06 Dec 1997 07:10:35 -0600 To: freebsd-isp@freebsd.org From: Kevin Brown Subject: multiple domains with sendmail Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings... This is really an elementary question, and I'm abit embarrassed to ask it, but since I've never had to deal with it before I will. We've got a machine running sendmail (not our primary mailserver) but now I need to be able to accept and pass mail for two domains. How do I go about accomplishing this? BTW: the sendmail server is in our DMZ, relaying mail back to our internal (AS/400) mail server, and doing a sender field re-write on all outgoing mail. ////////////////////////////////////////////////////////////////////// Kevin Brown Networking Engineer Huber & Associates IBM Business Partner http://www.primelink.com/haa/haahome.htm Phone: 573-634-5000 ext 114 Fax: 573-634-5500 ////////////////////////////////////////////////////////////////////// IBM, Cisco & Ascend Routers, Switches, HUBs, and related hardware. OS/2, Windows 3.x/95/NT, AIX, BSDI, FreeBSD, OS/400 and other OS's. RS6000, AS/400 and basic PC troubleshooting. ////////////////////////////////////////////////////////////////////// ------------------------------------------------------------------ Pursuate to US Code, Title 47, Chapter 5, Subchapter II, Sec. 227, any and all nonsolicited commercial E-mail sent to this address is subject to a download and archival fee in the amount of $500 US. Emailing denotes acceptance of these terms. ------------------------------------------------------------------ From owner-freebsd-isp Sat Dec 6 06:35:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA22013 for isp-outgoing; Sat, 6 Dec 1997 06:35:02 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from federation.addy.com (federation.addy.com [207.239.68.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA21991 for ; Sat, 6 Dec 1997 06:34:53 -0800 (PST) (envelope-from fbsdlist@federation.addy.com) Received: from localhost (fbsdlist@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id JAA06954; Sat, 6 Dec 1997 09:34:45 -0500 (EST) Date: Sat, 6 Dec 1997 09:34:45 -0500 (EST) From: Cliff Addy To: Jeff Lynch cc: "Bryn Wm. Moslow" , freebsd-isp@FreeBSD.ORG, jayk@nwlink.com Subject: Re: Adaptec 2940/Seagate Failures In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Dec 1997, Jeff Lynch wrote: > On Fri, 5 Dec 1997, Bryn Wm. Moslow wrote: > > > breath. The people who DO seem to be having problems are running the 2940 > > under heavy load conditions and having to power cycle servers at horrible > > Possibly a flakey controller? No, we have a half-dozen servers running 2.2.2 and 2940s and they *all* have this problem. These servers were built over a period of a year, so it's not a "bad batch" of controllers, either. The thing that consistently flips them out is a tape write error, although they regularly do it when NO tape i/o is happening. As someone noted earlier, the SCSI code is not very tolerant of errors and is being completely rewritten. The situation can be summarized: - The problem is real, it's not imaginary - It's widespread and common - It's in FBSD - It's being (hopefully) fixed Until then, all we can do is live with it and hope that a future release will let me go back to sleeping easily :) Cliff From owner-freebsd-isp Sat Dec 6 08:27:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA28143 for isp-outgoing; Sat, 6 Dec 1997 08:27:45 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from mercury.jorsm.com (mercury.jorsm.com [207.112.128.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA28135 for ; Sat, 6 Dec 1997 08:27:41 -0800 (PST) (envelope-from jeff@mercury.jorsm.com) Received: from localhost (jeff@localhost) by mercury.jorsm.com (8.8.7/8.8.7) with SMTP id KAA06773; Sat, 6 Dec 1997 10:27:38 -0600 (CST) Date: Sat, 6 Dec 1997 10:27:37 -0600 (CST) From: Jeff Lynch To: Jacob Suter cc: freebsd-isp@freebsd.org Subject: Re: Portslave? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 6 Dec 1997, Jacob Suter wrote: > Has anyone checked out portslave? It compiled fine in a test Slackware > box, but it doesn't seem to want to work in FreeBSD. My C skills are > nearly nonexistant when it comes to porting stuff from Linux to FreeBSD... > > The website is http://homepage.cistron.nl/~miquels/radius/.... They also > have a radius server and some other goodies on there (for the record the > radius server works fine in FreeBSD, go figure). > > Portslave is actually a PM2 emulator for Unix (linux apparently). Appears > to work nicely but I really don't want to think about running anything > that might actually need to be used on a regular basis under Linux. > > Thanks > Jacob Suter > Intrastellar Internet Service I have one running on a linux 2.0 kernel. It works reasonably well but I'm treating it as an experiment in trying to get cost/port down on NAS. But alas, it's about to be recomissioned for other server-based duties on FreeBSD as we are on the verge of converting everything to USR Total Control. For the record, this machine has had very few problems and has never crashed in the last year it's been in service. The main drawback with portslave, however, is until we have a well supported CT1 or PRI DSP/modem ISA/PCI card, forget 56K modems on this platform. Thats the mail reason for getting rid of it. BTW, Miquel is wonderful and provided excellent help the very few times I needed it getting started. ========================================================================= Jeffrey A. Lynch, President JORSM Internet email: jeff@jorsm.com Northwest Indiana's Full-Service Provider Voice: (219)322-2180 927 Sheffield Avenue, Dyer, IN 46311 Autoresponse: info@jorsm.com http://www.jorsm.com From owner-freebsd-isp Sat Dec 6 10:21:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA04267 for isp-outgoing; Sat, 6 Dec 1997 10:21:41 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from wicked.eaznet.com (wicked.eaznet.com [209.75.156.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA04241 for ; Sat, 6 Dec 1997 10:21:35 -0800 (PST) (envelope-from eddie@eaznet.com) Received: from eaznet.com (as1-05.eaznet.com [209.75.156.209]) by wicked.eaznet.com (8.8.7/8.8.5) with ESMTP id LAA25001; Sat, 6 Dec 1997 11:22:17 -0700 (MST) Message-ID: <345E05E5.A89F3E5D@eaznet.com> Date: Mon, 03 Nov 1997 10:12:05 -0700 From: Eddie Fry X-Mailer: Mozilla 4.03 [en] (WinNT; I) MIME-Version: 1.0 To: Dermot Bradley CC: Lukas Wunner , andrew@pubnix.net, kbrown@primelink.com, tomthai@future.net, dnelson@slip.net, rgrimes@GndRsh.aac.dev.com, bad@uhf.wireless.net, danny@panda.hilink.com.au, freebsd-isp@FreeBSD.ORG Subject: Re: Wireless Services References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The Aironet 640-2400 with the right antenna is capable of up to ~22 miles. ETSI 300 328 specifies 100mW max, but broadcast strength may reach 1W. So, using a 23dbi antennae and a 100mW box (with some loss due to lightening arresstors and cable) gives you about 1W of output which gives you about 22 miles of range. Eddie Dermot Bradley wrote: > On Fri, 31 Oct 1997, Lukas Wunner wrote: > > > Here in Germany (or rather, in all ETSI countries), the EIRP regulations > > are very strict, so even with the 18 dBi antennas, you cannot go > > further than about 2.5 km. > > ETSI 300 328 specifies 100mW max. I've used both Cylink (128k data rate) > at 5 miles (capable of 7 miles) and Wavelan-derived boxes (2Mb data rate) > at 1.5 miles (capable of 6km). I thought that the Breezecom boxes could do > approx. 6-7 miles. > > Dermot > > -- > Dermot Bradley > Belfast, Northern Ireland > bradley@oldcolo.com, bradley@debian.org -- Eddie Fry eddie@eaznet.com EAZNet Internet Services http://www.eaznet.com 220 West 7th Street Safford, AZ 85546 EAZing you into the future... From owner-freebsd-isp Sat Dec 6 12:04:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09420 for isp-outgoing; Sat, 6 Dec 1997 12:04:14 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from obiwan.TerraNova.net (root@obiwan.TerraNova.net [209.4.59.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA09414 for ; Sat, 6 Dec 1997 12:04:10 -0800 (PST) (envelope-from bofh@terranova.net) Received: from P1mpBSD.TerraNova.net (tog@guenhwyvar.TerraNova.net [209.4.59.4]) by obiwan.TerraNova.net (8.8.8/TerraNovaNet) with SMTP id PAA07216; Sat, 6 Dec 1997 15:07:50 -0500 (EST) Message-ID: <3489B051.615A@terranova.net> Date: Sat, 06 Dec 1997 15:06:41 -0500 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 3.03 (Win95; I) MIME-Version: 1.0 To: Cliff Addy CC: freebsd-isp@FreeBSD.ORG Subject: Re: Adaptec 2940/Seagate Failures References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Cliff Addy wrote: > No, we have a half-dozen servers running 2.2.2 and 2940s and they *all* > have this problem. These servers were built over a period of a year, so > it's not a "bad batch" of controllers, either. The thing that Do you also have this problem under 2.2.5-REL or 2.2.5-STABLE? There was some work done on the code between 2.2.2 and 2.2.5. Also, does anyone know if this problem persists in 3.0 at the moment? Don't think there was a problem in 2.1.x (but then it wasn't quite as fast either) -T -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- "Acceptance without proof is the fundamental characteristic of Western religion, Rejection without proof is the fundamental characteristic of Western science." -- Gary Zukav, "The Dancing Wu Li Masters" From owner-freebsd-isp Sat Dec 6 12:23:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA10671 for isp-outgoing; Sat, 6 Dec 1997 12:23:17 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA10659 for ; Sat, 6 Dec 1997 12:23:12 -0800 (PST) (envelope-from tim@shell.futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id OAA27959; Sat, 6 Dec 1997 14:23:05 -0600 (CST) Message-ID: <19971206142305.28932@futuresouth.com> Date: Sat, 6 Dec 1997 14:23:05 -0600 From: Tim Tsai To: "Bryn Wm. Moslow" Cc: freebsd-isp@FreeBSD.ORG, jayk@nwlink.com Subject: Re: Adaptec 2940/Seagate Failures References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Bryn Wm. Moslow on Fri, Dec 05, 1997 at 02:42:08PM -0800 Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bryn, we recently went through a similar set of problems on our news server and the following steps have solved the problem for us. We had nearly identical error messages as you, by the way. Our news server started with 9 SCSI hard disks (a combination of IBM and Quantum drives) across 3 controllers (2 Adaptec 2940UW and an NCR). While this setup would crash every now and then, it was tolerable and we only have to manually recover it once every month or so. The machine initially had 2.2-current but I upgraded to 3.0-current hoping it would fix the periodic problem. It didn't help at all. When I had to pull the NCR controller out for another machine in an emergency everything started to fall apart. We would get the same type of messages as you did requiring a manual "fsck" each time it crashed. It was rare that it ran for more than 3 days without crashing, usually during news.daily or network backup, or both. So this was obviously I/O load related. After checking cables, termination, software, etc. we finally came to an arrangement that has been super stable for us: 1) Enable SCAM support on all controllers. I don't know whether this helped anything or not but somebody on the list advocated it and it hasn't hurt us so I left it. 2) Disabled all the AHC_* options. For our hardware setup and load these options haven't been necessary. I am sure we lose some performance but it is not noticeable. When I am bored I may enable them again just to see what happens. 3) I ran find and looked for all the files outside of /dev that either does not belong to a user (-nouser), does not belong to a group (-nogroup), or is a character/block special device (-c -or -b). I found that fsck doesn't always clean up the file system as it should and left some of these special case files (usually with a crazy user id like 6123462). When these files are subsequently accessed, the machine crashed (obviously). You should first get a list of these files and inode numbers, take the machine to single user mode, run "clri" on these inode numbers, and then run fsck again. 4) Upgrade your motherboard to the latest BIOS. This completely cleared up our problems. I feel that if you do at least #1 and #3 it should fix your problems, barring any hardware issues. BTW, we are still running mixed wide/narrow drives on the same controller. We've never had a problem with that, although the narrow drives go to the narrow connector on the controller and vice versa, without any kind of adapters. Hope that helps, Tim On Fri, Dec 05, 1997 at 02:42:08PM -0800, Bryn Wm. Moslow wrote: > From: "Bryn Wm. Moslow" > To: freebsd-isp@FreeBSD.ORG > cc: jayk@nwlink.com > Subject: Adaptec 2940/Seagate Failures > Message-ID: > MIME-Version: 1.0 > Content-Type: TEXT/PLAIN; charset=US-ASCII > Sender: owner-freebsd-isp@FreeBSD.ORG > X-Loop: FreeBSD.org > Precedence: bulk > Hello, sorry that this is a bit windy but I'm desperate: > > I'm still having big problems with FreeBSD, the Adaptec 2940UW, and > Seagate Drives. When the system gets heavily loaded (i.e. 65-75 sendmail > processes, 20 or so poppers,) often it comes to a complete stop and sure > enough I can get to the console and discover just about the same thing > every time (which is at the bottom of this message along with my dmesg > output for informational purposes.) I've tried FreeBSD's both 2.2.2 and > 2.2.5, sendmail 8.8.5, 8.8.6, 8.8.7, 8.8.8, qpopper 2.3, 2.4. I would like > to note that disk I/O was much smoother and system load was significantly > lower with 2.2.5 but it was only two hours under load before it pooped the > first time as opposed to a couple days under 2.2.2. In fact, it was odd > because the load was 0.7 and iostat was about 3800sps on sd2 average when > the most recent death (see 'the hell' below) occured. > > I've been reading the long debate about the 2940 and FreeBSD for some time > and just today went through my whole archive of freebsd-isp and noted some > things. What especially stands out is the number of people saying that > they have no problem, "it works great," and then noting that they're not > really using it or only have a tape attached, etc., literally in the same > breath. The people who DO seem to be having problems are running the 2940 > under heavy load conditions and having to power cycle servers at horrible > times like myself. If you have an archive of freebsd-isp do a search on > "Adaptec 2940" and you'll see what I'm talking about. Just an observation > and opinion: I'm not trying to PO anyone but I think there has to be more > attention paid to the stability of the SCSI subsystem, specifically under > heavy loads. Once again: I love you all, I love Chuck, please help me ;). > > Notes: > > - I've used every combination of AHC_TAGENABLE, AHC_SCBPAGING_ENABLE, and > AHC_ALLOW_MEMIO in the kernel possible and each one in cooperation with > the others or on its own eventually brings down the system. > > - We've broken out the mail spool for local mail to a directory structure > based on the first letters of username such as: /var/mail/u/us/username. > This has helped overall but iostat still hits the roof when people get > lots of mail (lists, spam) and pop3 is yanking down large mail files. > > - per advice from other FreeBSD users and non-FreeBSD users and an > electrical engineer, the narrow drive on a separate controller from the > wide drives. > > - The drives are all internal, the bus is terminated and the cable is only > 0.5m. > > - The controller is in Ultra mode and I would like to keep it there if > possible. I've tried it without to no avail anyway. I'm quite sure this > should not be a problem as I have a BSDI 3.0 box running news that does at > least ten times the I/O per day at a higher load on two Adaptec 2940's and > 10 drives in Ultra mode with a 4-disk ccd (sp0 in BSDI) with the same CPU, > but I want to believe in the power of FreeBSD. :) > > The hell: (This particular kernel was with AHC_SCBPAGING_ENABLE but I get > similar results with the other options and ultimately a bus failure > and/or lockup and/or panic. I don't have as much trouble with > no extra ahc options but the system gets VERY s-l-o-w under load.) > > SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued \M^?\^OA Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xe6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): abort message in message buffer > sd2(ahc1:2:0): SCB 0x0 - timed out in message in phase, SCSISIGI == 0xf6 > SEQADDR = 0xd1 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x3 > sd2(ahc1:2:0): no longer in timeout > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > > dmesg output: (No ahc kernel options) > > FreeBSD 2.2.2-RELEASE #0: Wed Nov 19 13:31:09 PST 1997 > bryn@alabama.nwlink.com:/usr/src/sys/compile/ALABAMA > CPU: Pentium Pro (199.43-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x619 Stepping=9 > Features=0xfbff,MTRR,PGE,MCA,CMOV> > real memory = 268435456 (262144K bytes) > avail memory = 257245184 (251216K bytes) > Probing for devices on PCI bus 0: > chip0 rev 2 on pci0:0 > chip1 rev 1 on pci0:1:0 > chip2 rev 0 on pci0:1:1 > vx0 <3COM 3C905 Fast Etherlink XL PCI> rev 0 int a irq 12 on pci0:9 > mii[*mii*] address 00:60:08:0a:42:32 > ahc0 rev 0 int a irq 10 on pci0:10 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > ahc0 waiting for scsi devices to settle > (ahc0:0:0): "SEAGATE ST52160N 0285" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 2069MB (4238282 512 byte sectors) > vga0 rev 0 on pci0:11 > ahc1 rev 0 int a irq 11 on pci0:12 > ahc1: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > ahc1 waiting for scsi devices to settle > (ahc1:1:0): "SEAGATE ST34572W 0718" type 0 fixed SCSI 2 > sd1(ahc1:1:0): Direct-Access 4340MB (8888924 512 byte sectors) > (ahc1:2:0): "SEAGATE ST34572W 0784" type 0 fixed SCSI 2 > sd2(ahc1:2:0): Direct-Access 4340MB (8888924 512 byte sectors) > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: NEC 72065B > fd0: 1.44MB 3.5in > npx0 flags 0x1 on motherboard > npx0: INT 16 interface > WARNING: / was not properly dismounted. > > Thanks for your time, > Bryn From owner-freebsd-isp Sat Dec 6 12:27:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA11016 for isp-outgoing; Sat, 6 Dec 1997 12:27:22 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA11002 for ; Sat, 6 Dec 1997 12:27:13 -0800 (PST) (envelope-from tim@shell.futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id OAA28028; Sat, 6 Dec 1997 14:27:06 -0600 (CST) Message-ID: <19971206142706.27627@futuresouth.com> Date: Sat, 6 Dec 1997 14:27:06 -0600 From: Tim Tsai To: Travis Mikalson Cc: "Bryn Wm. Moslow" , freebsd-isp@FreeBSD.ORG, jayk@nwlink.com Subject: Re: Adaptec 2940/Seagate Failures References: <3488A507.65CB@terranova.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <3488A507.65CB@terranova.net>; from Travis Mikalson on Fri, Dec 05, 1997 at 08:06:15PM -0500 Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I just had it happen a couple days ago as a matter of fact.. it wasn't > fatal at all, just a hiccup; I was working on the system at the time. > > sd1(ahc0:2:0): SCB 0x6 - timed out in command phase, SCSISIGI == 0x84 > SEQADDR = 0x4e SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 > Ordered Tag queued > sd1(ahc0:2:0): SCB 0x7 timedout while recovery in progress > sd0(ahc0:0:0): SCB 0x0 timedout while recovery in progress > sd1(ahc0:2:0): SCB 0x2 timedout while recovery in progress > Ordered Tag sent > sd0(ahc0:0:0): SCB 0x3 timedout while recovery in progress > sd0(ahc0:0:0): SCB 0x1 timedout while recovery in progress > sd1(ahc0:2:0): SCB 0x6 - timed out in command phase, SCSISIGI == 0x84 > SEQADDR = 0x4e SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 > sd1(ahc0:2:0): abort message in message buffer > sd1(ahc0:2:0): SCB 6 - Abort Tag Completed. > sd1(ahc0:2:0): no longer in timeout > sd1(ahc0:2:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, > SCSISIGI == 0x0 > SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > Ordered Tag queued > sd1(ahc0:2:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, > SCSISIGI == 0x0 > SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > sd1(ahc0:2:0): Queueing an Abort SCB > sd1(ahc0:2:0): Abort Message Sent > sd1(ahc0:2:0): SCB 7 - Abort Tag Completed. > sd1(ahc0:2:0): no longer in timeout > Ordered Tag sent > > There did happen to be a higher than normal load on the system at the > time. > I've changed the cable thrice and the heat seems well within acceptable > parameters. Our experience is that these always develop into more serious problems. Run find on the file system and make sure you don't have any oddball files (I look for character/block special files and files without valid user id or group id). Tim From owner-freebsd-isp Sat Dec 6 12:40:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA11965 for isp-outgoing; Sat, 6 Dec 1997 12:40:07 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from magicnet.magicnet.net (root@magicnet.magicnet.net [204.96.116.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA11955 for ; Sat, 6 Dec 1997 12:40:03 -0800 (PST) (envelope-from bill@bilver.magicnet.net) Received: from bilver.magicnet.net (root@localhost) by magicnet.magicnet.net (8.8.6/8.8.6) with UUCP id PAA20851 for freebsd-isp@freebsd.org; Sat, 6 Dec 1997 15:39:42 -0500 (EST) Received: (from bill@localhost) by bilver.magicnet.net (8.8.5/8.7.3) id PAA16515 for freebsd-isp@freebsd.org; Sat, 6 Dec 1997 15:17:13 -0500 (EST) From: Bill Vermillion Message-Id: <199712062017.PAA16515@bilver.magicnet.net> Subject: Multiple domains with sendmail To: freebsd-isp@freebsd.org Date: Sat, 6 Dec 1997 15:17:13 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Recently Kevin Brown said: > Greetings... > This is really an elementary question, and I'm abit embarrassed to ask it, > but since I've never had to deal with it before I will. > We've got a machine running sendmail (not our primary mailserver) but now I > need to be able to accept and pass mail for two domains. How do I go about > accomplishing this? Use the Cw line or the Fw file and put the names in it. I have about 50 domains all being used by one mailserver. That parts is easy. Other parts of sendmail become somewhat mind-numbing. Bill -- bill@bilver.magicnet.net | bill@bilver.com