From owner-freebsd-isp Sun Sep 22 12:23:47 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA21004 for isp-outgoing; Sun, 22 Sep 1996 12:23:47 -0700 (PDT) Received: from mailgate ([202.159.65.166]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA20348; Sun, 22 Sep 1996 12:22:53 -0700 (PDT) Received: from manado.wasantara.net.id (manado.wasantara.net.id [202.159.87.163]) by mailgate (8.6.11/8.6.9) with ESMTP id CAA04057; Mon, 23 Sep 1996 02:10:35 +0700 Date: Mon, 23 Sep 1996 02:10:35 +0700 Received: from MANADO/SpoolDir by manado.wasantara.net.id (Mercury 1.21); 23 Sep 96 03:20:36 GMT+0800 Received: from SpoolDir by MANADO (Mercury 1.21); 23 Sep 96 03:20:04 GMT+0800 Received: from bandung.wasantara.net.id by manado.wasantara.net.id (Mercury 1.21); 23 Sep 96 03:19:54 GMT+0800 X-Sender: park@manado.wasantara.net.id (Unverified) X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-questions@freebsd.org From: Park Subject: Help!?!?!?!?!?! Cc: freebsd-isp@freebsd.org Message-ID: <1B5D4F7ECF@manado.wasantara.net.id> Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I tried to make a SLIP connection to my ISP. But after the link got established, my computer refused to assign the IP address to the sl0 device. My ISP uses dynamic SLIP, so I do not need to know the IP address which should be assigned to sl0 before the connection established. From owner-freebsd-isp Sun Sep 22 12:24:18 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA21369 for isp-outgoing; Sun, 22 Sep 1996 12:24:18 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA21107; Sun, 22 Sep 1996 12:23:56 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id VAA00335; Sun, 22 Sep 1996 21:00:46 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.6/8.7.3) with SMTP id UAA05630; Sun, 22 Sep 1996 20:08:46 +0200 (MET DST) Date: Sun, 22 Sep 1996 20:08:46 +0200 (MET DST) From: Andreas Klemm To: "Rodney W. Grimes" cc: isp@freebsd.org, hardware@freebsd.org Subject: Re: INN history file and disk I/O In-Reply-To: <199609182104.OAA04861@GndRsh.aac.dev.com> Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Rod ! What do you think about the Tyan boards ? Tomcat I and II ? I bought a Tomcat II for my wife. It always rebooted when enabling the L2 cache. My hardware dealer, which has good connections to Tyan, told me after 3 days (fast! ;) that the mainboard had a defect and a whole charge of 512k burst cache modules was bad as well. Now I have to wait for a new Tomcat II and L2 cache for about a week. I get brand new parts from US... I'm just curious, if I bought a good or a bad one. Test in magazines tell, that the boards are ok, only problems with 64MB Ram chips ... What do you think ?! Question to a MB guru ! ;-)) Andreas /// andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-isp Sun Sep 22 12:25:18 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA21820 for isp-outgoing; Sun, 22 Sep 1996 12:25:18 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA21727; Sun, 22 Sep 1996 12:25:05 -0700 (PDT) Received: from mailgate ([202.159.65.166]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id MAA02354 ; Sun, 22 Sep 1996 12:24:56 -0700 (PDT) Received: from manado.wasantara.net.id (manado.wasantara.net.id [202.159.87.163]) by mailgate (8.6.11/8.6.9) with ESMTP id CAA04065; Mon, 23 Sep 1996 02:11:14 +0700 Date: Mon, 23 Sep 1996 02:11:14 +0700 Received: from MANADO/SpoolDir by manado.wasantara.net.id (Mercury 1.21); 23 Sep 96 03:21:11 GMT+0800 Received: from SpoolDir by MANADO (Mercury 1.21); 23 Sep 96 03:20:43 GMT+0800 Received: from bandung.wasantara.net.id by manado.wasantara.net.id (Mercury 1.21); 23 Sep 96 03:20:33 GMT+0800 X-Sender: park@manado.wasantara.net.id (Unverified) X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-questions@freebsd.org From: Eka Kelana Subject: Help !?!?!?!?! Cc: freebsd-isp@freebsd.org Message-ID: <1B601F107E@manado.wasantara.net.id> Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I tried to make a SLIP connection to my ISP. But after the link got established, my computer refused to assign the IP address to the sl0 device. My ISP uses dynamic SLIP, so I do not need to know the IP address which should be assigned to sl0 before the connection established. I used DIP to make SLIP connection with my ISP. I usually invoke #dip -t to start a DIP session, then I use term command inside DIP to dial my ISP's remote machine manually. After the connection has established (indicated by line "CONNECT" followed by "9600" below it) then I will be prompted "Login:" and I have to enter my user name and then the password to log into the remote machine. After logging in, I should invoke SLIP in remote machine to start SLIP session. The remote machine will then indicate that a SLIP session has been started by sending line "The assigned IP address is xxxx.xxxx.xxxx.xxxx" followed by "SLIP mode enabled" below it. I used another tty or xterm (if I use XWindow system) to invoke slattach and adding the default route : #slattach -h -s 9600 /dev/cuaa1 (worked well) #route add default xxxx.xxxx.xxxx.xxxx (---> this is the IP address assigned by my ISP) But my sistem confusingly refused to add the route into the routing table by saying "Host is unreachable". Well, up to this point, I thought that route command should work well because I have attached the sl0 device to the cuaa1 device, through which the assigned IP address will be sent and be assigned to sl0 device. Am I right? But it didn't. I couldn't even "ping" the assigned IP address (xxxx.xxxx.xxxx.xxxx) Note: I used to use Linux to connect with my ISP, and all command invocation above worked well. I have configured the sl0 device in /etc/sysconfig and I just put "up" after "ifconfig_sl0=" line (becomes ----> ifconfig_sl0="up"). Somebody here please help me ... I would be very grateful for the help. ********** Eka Kelana ********** * I would like to thank Mr. Gary Chrysler (tcg@ime.net) who has helped me to set up my PPP. Well it's still not working till now and I've decided to use SLIP instead. From owner-freebsd-isp Sun Sep 22 12:40:39 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02114 for isp-outgoing; Sun, 22 Sep 1996 12:40:39 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02028; Sun, 22 Sep 1996 12:40:31 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id MAA00698; Sun, 22 Sep 1996 12:40:01 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609221940.MAA00698@GndRsh.aac.dev.com> Subject: Re: INN history file and disk I/O In-Reply-To: from Andreas Klemm at "Sep 22, 96 08:08:46 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Sun, 22 Sep 1996 12:40:01 -0700 (PDT) Cc: isp@freebsd.org, hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi Rod ! > > What do you think about the Tyan boards ? Tomcat I and II ? >From the data sheets they look fine, from what others have been saying about success with using them they look fine. First hand I don't have any experience, though that will be changing soon enough. > > I bought a Tomcat II for my wife. It always rebooted when enabling > the L2 cache. My hardware dealer, which has good connections to Tyan, > told me after 3 days (fast! ;) that the mainboard had a defect and > a whole charge of 512k burst cache modules was bad as well. > > Now I have to wait for a new Tomcat II and L2 cache for about a week. > I get brand new parts from US... > > I'm just curious, if I bought a good or a bad one. Test in magazines > tell, that the boards are ok, only problems with 64MB Ram chips ... > > What do you think ?! Question to a MB guru ! ;-)) > > Andreas /// > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-isp Sun Sep 22 21:39:05 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA07258 for isp-outgoing; Sun, 22 Sep 1996 21:39:05 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA07239; Sun, 22 Sep 1996 21:39:01 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id SAA00371; Sun, 22 Sep 1996 18:40:56 -0700 (PDT) Date: Sun, 22 Sep 1996 18:40:56 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Eka Kelana cc: freebsd-questions@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Help !?!?!?!?! In-Reply-To: <1B601F107E@manado.wasantara.net.id> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 23 Sep 1996, Eka Kelana wrote: > I tried to make a SLIP connection to my ISP. But after the link got > established, my computer refused to assign the IP address to the sl0 device. > My ISP uses dynamic SLIP, so I do not need to know the IP address which > should be assigned to sl0 before the connection established. > I used another tty or xterm (if I use XWindow system) to invoke slattach > and adding the default route : > > #slattach -h -s 9600 /dev/cuaa1 (worked well) > #route add default xxxx.xxxx.xxxx.xxxx (---> this is the IP address assigned > by my ISP) Shouldn't this be the other host's address? For my PPP connections (using ppp(1)) I have it add a default route to the remote and it works fine. 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 Sun Sep 22 22:31:51 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA07359 for isp-outgoing; Sun, 22 Sep 1996 22:31:51 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA07332 for ; Sun, 22 Sep 1996 22:31:48 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id BAA23588 for ; Mon, 23 Sep 1996 01:31:47 -0400 (EDT) Date: Mon, 23 Sep 1996 01:31:47 -0400 (EDT) From: Brian Tao To: FREEBSD-ISP-L Subject: Thoughts on a news server cluster Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The stuff I've been posting about hardware RAID products will ultimately lead to the installation of a news server cluster. I've been running fairly happily so far on a single P133 with 128MB, 3 NCR53810 controllers and 9 drives. No RAID, no ccd... just different drives mounted at different points in the filesystem. The concurrency is actually fairly decent, looking at iostat. Anyhow, management has decided they want something more robust and survivable, and that has led me down the path of redundant and high-availability hardware without having to switch to some commercial OS vendor. ;-) I've read a lot of discussion on building scalable, reliable news server configurations. I'd like to know if anyone has some wisdown to share on the FreeBSD specifics. For example, someone mentioned that ccd did not appear to be all that stable in -current. Would using 2.1.5-RELEASE be better? Another thread mentioned that heavy NFS client activity causes instability. Should I then avoid NFS altogether and pay a premium for a local disk subsystem for each server? This is the configuration I'm looking at. There will be three PPro200 servers on a 100MB Ethernet segment. One will be dedicated to incoming and outgoing feeds. The other two will be for readers. The feeder server will have 4x2GB of local storage, holding about 2 days of news. It will handle all transactions with other servers and not have to deal with NNRP reading or posting. One of its feeds will be to the primary reader server. This reader server will be a full news server in its own right, except that it has just the one single upstream feed. I shouldn't have to mess around with XREPLIC or NFS-mounting a huge spool off a busy feeder server. The primary reader server will have 16x2GB drives, RAID 5 with hot spares, two fast/wide controllers, 8 drives per controller. It exchanges articles with the main feeder server as well as accepting NNRP connections. I figure with just a single feed, I should be able to avoid the problem of long newsreader startup delays because innd is blocked on one of its connections. Secondary reader servers will simply NFS-mount the spool as read-only and run in.nnrpd -S out of inetd. With the sharedactive patch, each 256MB reader server should be able to handle 500 to 600 readers at once, based on my experiences with my current news server. 128MB on the feeder server should be more than enough for a few dozen feeds. This setup can then be replicated to serve different geographical regions, with only the feeder servers exchanging traffic to save on WAN bandwidth. Any caveats I should look out for, especially with NFS and ccd? Any other recommendations (besides getting more RAM ;-))? Have there been any significant improvements to the AHA-2940UW driver in 2.2 that isn't in 2.1.5? -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-isp Mon Sep 23 04:06:53 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA04426 for isp-outgoing; Mon, 23 Sep 1996 04:06:53 -0700 (PDT) Received: from wizard.teksupport.net.au (wizard.teksupport.net.au [203.17.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA04388 for ; Mon, 23 Sep 1996 04:06:45 -0700 (PDT) Received: from magician.teksupport.net.au (magician.teksupport.net.au [203.17.1.98]) by wizard.teksupport.net.au (8.6.11/8.6.9) with SMTP id VAA23396 for ; Mon, 23 Sep 1996 21:06:40 +1000 Message-Id: <199609231106.VAA23396@wizard.teksupport.net.au> X-Sender: robseco1@wizard.teksupport.net.au X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 23 Sep 1996 21:06:41 +1100 To: freebsd-isp@freebsd.org From: Rob Secombe Subject: mb_map full Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Every 'once in a blue moon' ( 3-6 months) one of our servers crashes with the following error: Sep 23 02:24:26 wizard kernel: mb_map full Before anyone says anything, I know I need to upgrade this machine to 2.1.5. However, aside from this problem it runs flawlessly and the upgrade is planned for next month. It is currently running FreeBSD 2.0-RELEASE GENERIC kernel. I have had a rumage through the books but haven't found anything as yet. If anyone is able to shed some light on this I would appreciate it. Regards to all Rob Secombe Teksupport Pty. Ltd. 7 Warwick Avenue, Springvale, Email robseco@wizard.teksupport.net.au Melbourne 3171 Victoria Australia World Wide Web http://www.teksupport.net.au/ ************************************************************************* From owner-freebsd-isp Mon Sep 23 05:02:38 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA02789 for isp-outgoing; Mon, 23 Sep 1996 05:02:38 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA02758 for ; Mon, 23 Sep 1996 05:02:33 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id FAA01699; Mon, 23 Sep 1996 05:03:08 -0700 (PDT) Message-Id: <199609231203.FAA01699@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Rob Secombe cc: freebsd-isp@freebsd.org Subject: Re: mb_map full In-reply-to: Your message of "Mon, 23 Sep 1996 21:06:41 +1100." <199609231106.VAA23396@wizard.teksupport.net.au> From: David Greenman Reply-To: dg@root.com Date: Mon, 23 Sep 1996 05:03:08 -0700 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Every 'once in a blue moon' ( 3-6 months) one of our servers crashes with >the following error: > >Sep 23 02:24:26 wizard kernel: mb_map full > >Before anyone says anything, I know I need to upgrade this machine to 2.1.5. >However, aside from this problem it runs flawlessly and the upgrade is >planned for next month. It is currently running FreeBSD 2.0-RELEASE GENERIC >kernel. You can work around this by adding options "NMBCLUSTERS=" to your kernel config file - where is a number like 4000 or so. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-isp Mon Sep 23 05:10:38 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA07684 for isp-outgoing; Mon, 23 Sep 1996 05:10:38 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA07618; Mon, 23 Sep 1996 05:10:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id FAA01714; Mon, 23 Sep 1996 05:11:56 -0700 (PDT) Message-Id: <199609231211.FAA01714@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: isp@freebsd.org cc: chat@freebsd.org Subject: fast ethernet hub for sale From: David Greenman Reply-To: dg@root.com Date: Mon, 23 Sep 1996 05:11:56 -0700 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In order to get our various fast ethernet drivers working in full duplex mode, I've purchased an ethernet switch. In order to pay for this I need to sell my D-Link 12 port 100BASE-TX hub. $975. OBO. I also have 4 new D-Link 10/100Mbps cards (DEC 21140 chip based and work fine with FreeBSD) that I'd like to sell. $80/each. Send me email if you're interested in any of this. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-isp Mon Sep 23 07:21:19 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA14600 for isp-outgoing; Mon, 23 Sep 1996 07:21:19 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA14577 for ; Mon, 23 Sep 1996 07:21:15 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id JAA15753; Mon, 23 Sep 1996 09:20:09 -0500 From: Joe Greco Message-Id: <199609231420.JAA15753@brasil.moneng.mei.com> Subject: Re: Thoughts on a news server cluster To: taob@io.org (Brian Tao) Date: Mon, 23 Sep 1996 09:20:09 -0500 (CDT) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: from "Brian Tao" at Sep 23, 96 01:31:47 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The stuff I've been posting about hardware RAID products will > ultimately lead to the installation of a news server cluster. I've > been running fairly happily so far on a single P133 with 128MB, 3 > NCR53810 controllers and 9 drives. No RAID, no ccd... just different > drives mounted at different points in the filesystem. The concurrency > is actually fairly decent, looking at iostat. You get more concurrency if you use ccd too :-) One of my pets: /dev/ccd3e 1971087 765364 1048037 42% /nov /dev/ccd2e 1971087 357161 1456240 20% /usr/local /dev/ccd0e 3899273 2478146 1109185 69% /news /dev/ccd1e 3899273 1705248 1882083 48% /news/.0 /dev/ccd4e 8075148 5569491 1859646 75% /news/.1 > Anyhow, management has decided they want something more robust and > survivable, and that has led me down the path of redundant and > high-availability hardware without having to switch to some commercial > OS vendor. ;-) I've read a lot of discussion on building scalable, > reliable news server configurations. I'd like to know if anyone has > some wisdown to share on the FreeBSD specifics. If nothing else, you can get a "SCSI-SCSI" translator (made by Mylex and others) where you just provide a fast/wide SCSI adaptor (2940, etc) and let the black box handle the RAID aspects. Support is probably going to appear for several host adapter RAID solutions in the not too distant future, if I believe what people are telling me :-) > For example, someone mentioned that ccd did not appear to be all > that stable in -current. Would using 2.1.5-RELEASE be better? Proudly running ccd since 2.1.0-R without a hiccup. Or at least, a hiccup that wasn't my own stupid fault for not reading the docs :-) > Another thread mentioned that heavy NFS client activity causes > instability. Should I then avoid NFS altogether and pay a premium for > a local disk subsystem for each server? Is there any other way to do it??? You do NOT want to NFS mount!!! I have done it. If you have the I/O bandwidth and CPU (but not the RAM) to spare on a machine, it may be a worthwhile option... but the tax on the host is high. And you take a major reliability hit if that host goes down. If you add additional disks with each additional slave, you are growing your I/O bandwidth in a nearly linear fashion (the exception: the feeder machine). While this is somewhat expensive, it is not terrible... the df output above is from a slave at Exec. It is 4 1G 31055N's, 4 32550N's, and 2 15150N's (soon to be Barra 9G's). At Exec, we discussed reliability in a lot of detail. We ended up agreeing that it was more reliable and more expandable simply to maintain N+1 servers where N was the number of systems I felt were required for their load. That means I can take ANY one machine out of the loop (even the central feeder, although obviously only for a short period of time) and not affect end user service in the least. For informational purposes, the service afforded by a system such as the following is excellent: ASUS P/E-mumble dual CPU/8 SIMM slot board P133 192MB RAM 3 NCR 810 1 SMC EtherPower 10/100 6 x ST32550N 4 x ST31055N 2 x ST15150N It gives me 9 days retention on most stuff, 12 on alt, 2 on alt.binaries. It supports 150 users and _flies_, and even at 200 the performance is "acceptable" (but starts to degrade.. pretty much simultaneously RAM and I/O bandwidth start to dry up). For us, it turned out to be cheaper to build these machines than it would have been to build somewhat beefier machines to support a few more readers per machine. Mostly a cost thing. But it's also much higher availability. As "N" grows, even the loss of two machines is less of a concern.. > This is the configuration I'm looking at. There will be three > PPro200 servers on a 100MB Ethernet segment. One will be dedicated to > incoming and outgoing feeds. The other two will be for readers. PPro200? Heavy iron for news... what exactly are you doing with all that horsepower... :-) > The feeder server will have 4x2GB of local storage, holding about > 2 days of news. It will handle all transactions with other servers > and not have to deal with NNRP reading or posting. One of its feeds > will be to the primary reader server. This reader server will be a > full news server in its own right, except that it has just the one > single upstream feed. I shouldn't have to mess around with XREPLIC or > NFS-mounting a huge spool off a busy feeder server. That is one way to handle it, but I find that running XREPLIC off of the feeds system is perfectly acceptable... if I was going to have a separate "reader" fan-out machine I would probably STILL run it as an XREPLIC slave from the feeder machine... convenience. > The primary reader server will have 16x2GB drives, RAID 5 with hot > spares, two fast/wide controllers, 8 drives per controller. It > exchanges articles with the main feeder server as well as accepting > NNRP connections. I figure with just a single feed, I should be able > to avoid the problem of long newsreader startup delays because innd is > blocked on one of its connections. Secondary reader servers will > simply NFS-mount the spool as read-only and run in.nnrpd -S out of > inetd. > > With the sharedactive patch, each 256MB reader server should be > able to handle 500 to 600 readers at once, based on my experiences I don't know, I would think that I would start seeing some I/O contention with just one machine.. And I have not seen any basis for supporting that many readers on a single machine.. how big is your active file? What does "top"'s output look like on one of your readers? Enquiring minds want to know :-) > with my current news server. 128MB on the feeder server should be > more than enough for a few dozen feeds. This setup can then be > replicated to serve different geographical regions, with only the > feeder servers exchanging traffic to save on WAN bandwidth. That's actually a case for XREPLIC... if all your news systems run in sync... think about it :-) > Any caveats I should look out for, especially with NFS and ccd? > Any other recommendations (besides getting more RAM ;-))? Have there > been any significant improvements to the AHA-2940UW driver in 2.2 that > isn't in 2.1.5? ... JG From owner-freebsd-isp Mon Sep 23 08:54:08 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17751 for isp-outgoing; Mon, 23 Sep 1996 08:54:08 -0700 (PDT) Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA17727 for ; Mon, 23 Sep 1996 08:53:58 -0700 (PDT) Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id IAA12960; Mon, 23 Sep 1996 08:52:19 -0700 Date: Mon, 23 Sep 1996 08:52:19 -0700 From: Jim Shankland Message-Id: <199609231552.IAA12960@saguaro.flyingfox.com> To: freebsd-isp@FreeBSD.ORG, robseco@wizard.teksupport.net.au Subject: Re: mb_map full Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Every 'once in a blue moon' ( 3-6 months) one of our servers > crashes with the following error: > > Sep 23 02:24:26 wizard kernel: mb_map full > > Before anyone says anything, I know I need to upgrade this > machine to 2.1.5. However, aside from this problem it runs > flawlessly and the upgrade is planned for next month. It is > currently running FreeBSD 2.0-RELEASE GENERIC kernel. Also `panic("kmem_malloc: kmem_map too small")' caused by, e.g., a fork() when running with high network activity (mbufs come out of the kmem_map) and little physical memory. Granted, when you're out of memory, you're out of memory, but returning EAGAIN instead of panicking would seem to be more in the spirit of graceful degradation :-). This was 2.1.0-RELEASE; haven't seen this yet under 2.1.5, and haven't yet taken a close look to see if it's been fixed; but the kmem_malloc code, at least, looks about the same as under 2.1.0. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-isp Mon Sep 23 14:36:35 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16619 for isp-outgoing; Mon, 23 Sep 1996 14:36:35 -0700 (PDT) Received: from other1.credo.net (nik@[205.230.204.29]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA16559 for ; Mon, 23 Sep 1996 14:36:27 -0700 (PDT) Received: (from nik@localhost) by other1.credo.net (8.7.5/8.7.3) id OAA00340 for isp@freebsd.org; Mon, 23 Sep 1996 14:33:55 -0700 (PDT) From: Nikolaus Spence Message-Id: <199609232133.OAA00340@other1.credo.net> Subject: UPS To: isp@freebsd.org Date: Mon, 23 Sep 1996 14:33:54 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk does anyone have any recommendations on a good UPS that can keep 6 systems up long enough to cleanly shutdown? -- Nikolaus Spence nik@darkstar.credo.net System Administrator Credo Computer Systems, Inc. -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzI252cAAAEEAKddY7NyNa5Mdm8s1OFegkfksR5lrLbes2VtwNoyYOUg0aPT AoE8HUMWysW44LwTJ7tdx6+lnWWIOLlcnxBSl2DcyPn8/vO0p5qugyvDxIW9c1Vr s0Awk8PkaaNsEO/UoaES+tfJw5RDxLXhxJr4ehMhn83G1sT9J8Og+rzTLMSpAAUR tB9OaWtvbGF1cyBTcGVuY2UgPG5pa0BjcmVkby5uZXQ+ =ScJz -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-isp Mon Sep 23 17:51:32 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA01861 for isp-outgoing; Mon, 23 Sep 1996 17:51:32 -0700 (PDT) Received: from m4.sprynet.com (m4.sprynet.com [165.121.1.96]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA01818 for ; Mon, 23 Sep 1996 17:51:28 -0700 (PDT) Received: from local.com (ad37-183.compuserve.com [199.174.140.183]) by m4.sprynet.com (8.6.12/8.6.12) with SMTP id RAA03657 for ; Mon, 23 Sep 1996 17:49:30 -0700 Message-Id: <199609240049.RAA03657@m4.sprynet.com> Comments: Authenticated sender is From: "Jesse" Organization: Brown Computing To: freebsd-isp@freebsd.org Date: Mon, 23 Sep 1996 17:49:36 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: DigiBoard? X-Confirm-Reading-To: "Jesse" X-pmrqc: 1 Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I was wondering if anyone had any opinions on a good 8 or 16 port DigiBoard for FreeBSD (2.1.5r) Thanks, Jesse ------------------------------------------ Brown computer repair and training. Phone (805) 942-1391 E-mail bextreme@sprynet.com From owner-freebsd-isp Mon Sep 23 20:24:37 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA00496 for isp-outgoing; Mon, 23 Sep 1996 20:24:37 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA00476 for ; Mon, 23 Sep 1996 20:24:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id UAA03226; Mon, 23 Sep 1996 20:25:38 -0700 (PDT) Message-Id: <199609240325.UAA03226@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Jim Shankland cc: freebsd-isp@freebsd.org, robseco@wizard.teksupport.net.au Subject: Re: mb_map full In-reply-to: Your message of "Mon, 23 Sep 1996 08:52:19 PDT." <199609231552.IAA12960@saguaro.flyingfox.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 23 Sep 1996 20:25:38 -0700 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Every 'once in a blue moon' ( 3-6 months) one of our servers >> crashes with the following error: >> >> Sep 23 02:24:26 wizard kernel: mb_map full >> >> Before anyone says anything, I know I need to upgrade this >> machine to 2.1.5. However, aside from this problem it runs >> flawlessly and the upgrade is planned for next month. It is >> currently running FreeBSD 2.0-RELEASE GENERIC kernel. > >Also `panic("kmem_malloc: kmem_map too small")' caused by, e.g., >a fork() when running with high network activity (mbufs come >out of the kmem_map) and little physical memory. Granted, when >you're out of memory, you're out of memory, but returning >EAGAIN instead of panicking would seem to be more in the spirit >of graceful degradation :-). > >This was 2.1.0-RELEASE; haven't seen this yet under 2.1.5, and >haven't yet taken a close look to see if it's been fixed; but >the kmem_malloc code, at least, looks about the same as under >2.1.0. The kmem_map full panic was the result of a mis-calculation of the size of the map in 2.1R. The calculation didn't account for the mb_map being a submap of it, and thus large mb_maps would leave little space left over for the [much more important] kmem_map. This was fixed in post-2.1 with the following commit: ---------------------------- revision 1.18 date: 1996/01/29 09:58:34; author: davidg; state: Exp; lines: +9 -7 Fixed two bugs in the calculation of the malloc area (kmem_map) size: 1) The calculation didn't account for NMBCLUSTERS, so if a large number of clusters was specified, it would leave little or no space for kernel malloc. 2) It was bogusly restricted to v_page_count. This doesn't take into account the sparseness of the malloc area and would have caused problems on machines with small amounts of memory. It should probably instead be changed to set the malloc limit to be constrained by the amount of memory, but I didn't do this. (#2 fixed in rev 1.19) ---------------------------- revision 1.12.4.1 date: 1996/01/29 11:20:25; author: davidg; state: Exp; lines: +13 -7 Retrofitted changes from revs 1.18 and 1.19: fix bugs with malloc area size calculations. ...rev 1.12.4.1 was the version released in 2.1.5R. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-isp Mon Sep 23 21:48:08 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA06600 for isp-outgoing; Mon, 23 Sep 1996 21:48:08 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA06532 for ; Mon, 23 Sep 1996 21:48:01 -0700 (PDT) Received: from eagle.bigblue.no (eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id GAA06956 for ; Tue, 24 Sep 1996 06:45:14 +0200 Message-Id: <199609240445.GAA06956@login.bigblue.no> From: "Frode Nordahl" To: "isp@FreeBSD.org" Date: Tue, 24 Sep 96 05:54:52 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: PMMail 1.52 For OS/2 UNREGISTERED SHAREWARE MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Huh? Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk What's this? ------ (top) Mem: 24M Active, 1352K Inact, 6000K Wired, 19M Cache, 6076K Buf, 12M Free Swap: 56M Total, 7012K Used, 49M Free, 12% Inuse ------ (top) 19 MB Cache, 12 MB Free ram, still, it swapps... Why is that?? From owner-freebsd-isp Tue Sep 24 00:04:37 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA08001 for isp-outgoing; Tue, 24 Sep 1996 00:04:37 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA07973 for ; Tue, 24 Sep 1996 00:04:33 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id AAA03539; Tue, 24 Sep 1996 00:05:46 -0700 (PDT) Message-Id: <199609240705.AAA03539@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Frode Nordahl" cc: "isp@FreeBSD.org" Subject: Re: Huh? In-reply-to: Your message of "Tue, 24 Sep 1996 05:54:52." <199609240445.GAA06956@login.bigblue.no> From: David Greenman Reply-To: dg@root.com Date: Tue, 24 Sep 1996 00:05:46 -0700 Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >What's this? > >------ (top) >Mem: 24M Active, 1352K Inact, 6000K Wired, 19M Cache, 6076K Buf, 12M Free >Swap: 56M Total, 7012K Used, 49M Free, 12% Inuse >------ (top) > >19 MB Cache, 12 MB Free ram, still, it swapps... Why is that?? It simply means that the system has pushed out some dirty pages during a time that the system required lots of memory. Whatever caused that demand has gone away now, but the pages are still stored in swap so that they may possibly be used again (the in-core copies reclaimed without having to re-page them out...assuming they aren't modified again). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-isp Tue Sep 24 07:43:39 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA16387 for isp-outgoing; Tue, 24 Sep 1996 07:43:39 -0700 (PDT) Received: from radio.nwpros.com (nwpros.com [205.229.128.214]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA16364 for ; Tue, 24 Sep 1996 07:43:32 -0700 (PDT) Received: from rickbox.nwpros.com (rickbox.nwpros.com [205.229.128.217]) by radio.nwpros.com (8.6.12/8.6.12) with SMTP id JAA15096; Tue, 24 Sep 1996 09:50:21 -0500 Message-Id: <1.5.4.32.19960924145849.00684ca4@nwpros.com> X-Sender: rickg@nwpros.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 24 Sep 1996 09:58:49 -0500 To: "Frode Nordahl" From: Rick Gray Subject: Re: Huh? Cc: isp@freebsd.org Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 05:54 AM 9/24/96, you wrote: >What's this? > >------ (top) >Mem: 24M Active, 1352K Inact, 6000K Wired, 19M Cache, 6076K Buf, 12M Free >Swap: 56M Total, 7012K Used, 49M Free, 12% Inuse >------ (top) > >19 MB Cache, 12 MB Free ram, still, it swapps... Why is that?? > Does it swap all the time or only when people are running a program? ************************************************ Rick Gray Director of Internet Services Network Pros, Inc. rickg@nwpros.com (713)780-5900 "It is a good day to die." ----Klingon Philosophy ************************************************ From owner-freebsd-isp Tue Sep 24 09:07:49 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA06820 for isp-outgoing; Tue, 24 Sep 1996 09:07:49 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA06762 for ; Tue, 24 Sep 1996 09:07:34 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id MAA08665; Tue, 24 Sep 1996 12:06:11 -0400 (EDT) Date: Tue, 24 Sep 1996 12:06:11 -0400 (EDT) From: Brian Tao Reply-To: Brian Tao To: Joe Greco cc: freebsd-isp@FreeBSD.ORG Subject: Re: Thoughts on a news server cluster In-Reply-To: <199609231420.JAA15753@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 23 Sep 1996, Joe Greco wrote: > > You get more concurrency if you use ccd too :-) True enough, but I didn't feel ccd was stable enough when I first built our news server (late last year). > If nothing else, you can get a "SCSI-SCSI" translator (made by Mylex > and others) where you just provide a fast/wide SCSI adaptor (2940, > etc) and let the black box handle the RAID aspects. Good news... Open Storage says they will have a 5x4GB CRD-5300 (might be a bit off on the model number) with 64MB cache available for me in the next couple of days. The PPro systems are arriving this afternoon, and I'm going to order a bunch of 2GB drives in a rackmount chassis for next week. That will give me one system with a single F/W drive, a ccd of 2GB drives, a Streamlogic hardware RAID and a CMD hardware RAID for benchmark comparisons. The bits will be flying. ;-) > Support is probably going to appear for several host adapter RAID > solutions in the not too distant future, if I believe what people are > telling me :-) Anything happening with the effort to pool some money together to pay a programmer to accelerate his port the DPT drivers? I *might* be able to convince the company to toss in some money towards such an effort. > You do NOT want to NFS mount!!! I have done it. If you have the I/O > bandwidth and CPU (but not the RAM) to spare on a machine, it may be a > worthwhile option... but the tax on the host is high. And you take a > major reliability hit if that host goes down. I'm trying to do a simple sort of cost-benefit analysis. Two F/W controllers and level 5 RAID with 25GB of usuable capacity costs in the $25000 range. Per machine. For that kind of money, I'm definitely willing to give NFS-mounted reader servers a try. > It gives me 9 days retention on most stuff, 12 on alt, 2 on > alt.binaries. It supports 150 users and _flies_, and even at 200 the > performance is "acceptable" (but starts to degrade.. pretty much > simultaneously RAM and I/O bandwidth start to dry up). The only performance problem I'm seeing is long delays or timeouts when attempting to open an NNRP session. Once I'm in, the server is niec and fast. I haven't tried anything special with starting in.nnrpd's out of inetd and running innd on a different port, etc. It seems to be related to the number of incoming innxmit connections. > PPro200? Heavy iron for news... what exactly are you doing with all > that horsepower... :-) They were roughly same price as Pentium 200's (a couple hundred dollars difference). Maybe I'll start playing with on-the-fly compression of news articles. ;-) > That is one way to handle it, but I find that running XREPLIC off of > the feeds system is perfectly acceptable... if I was going to have a > separate "reader" fan-out machine I would probably STILL run it as an > XREPLIC slave from the feeder machine... convenience. I don't want to "lock" myself into using XREPLIC though. If the main feeder blows up and I have to newfs the spool, it'll take extra work to resync those article numbers. If I just treat the feeder and the primary reader machine as entirely autonomous servers, something that goes wrong with one is less likely to affect the other. Also, isn't slave mode required for XREPLIC? If the feeder server is unavailable, none of the reader machines will be able to post. I've not played with XREPLIC before, so my understanding may be off. > I don't know, I would think that I would start seeing some I/O > contention with just one machine.. I don't think we're going to hit 1000 simultaneous readers at this POP for a while yet. It will be a gradual curve up, so any anticipated I/O bottlenecks can be headed off before they become a problem. Do we have any kernel optimizations yet for PPro memory- intensive operations? > And I have not seen any basis for supporting that many readers on a > single machine.. how big is your active file? What does "top"'s > output look like on one of your readers? Enquiring minds want to know :-) It's a pretty small active file, just under 9000 groups (407187 bytes). 'top' looks like this: load averages: 0.36, 0.42, 0.41 11:52:58 109 processes: 1 running, 118 sleeping Cpu states: 2.7% user, 1.5% nice, 14.2% system, 2.3% interrupt, 79.2% idle Mem: 82M Active, 6152K Inact, 20M Wired, 19M Cache, 7785K Buf, 176K Free Swap: 262M Total, 8336K Used, 254M Free, 3% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 27230 news -6 0 24M 24M biowai 95:05 13.08% 11.02% innd.nodebug 27238 root 29 0 352K 808K RUN 0:00 3.15% 0.57% top 26658 news 2 4 316K 708K select 0:01 0.38% 0.38% in.nnrpd 25061 news 2 0 220K 352K sbwait 0:22 0.31% 0.31% innxmit 27200 news 2 4 292K 868K sbwait 0:00 0.23% 0.23% in.nnrpd 27235 news 2 0 292K 992K select 0:00 0.38% 0.19% in.nnrpd 27233 news -6 0 152K 484K piperd 0:00 0.20% 0.15% overchan 27150 news 2 4 288K 728K sbwait 0:00 0.08% 0.08% in.nnrpd 27190 news 2 4 284K 692K sbwait 0:00 0.08% 0.08% in.nnrpd 26803 news 2 4 292K 732K sbwait 0:00 0.04% 0.04% in.nnrpd 26480 news 2 0 448K 548K select 0:04 0.04% 0.04% innxmit 23024 news 2 0 220K 308K sbwait 0:31 0.04% 0.04% innxmit [...] Assuming 32MB for kernel and OS stuff, 32MB for innd, 150MB for 500 readers and no feeds, that still leaves ~40MB for disk cache and other processes (like expires) on a 256MB machine. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-isp Tue Sep 24 09:32:13 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA16875 for isp-outgoing; Tue, 24 Sep 1996 09:32:13 -0700 (PDT) Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA16819 for ; Tue, 24 Sep 1996 09:32:05 -0700 (PDT) Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id JAA13814; Tue, 24 Sep 1996 09:30:24 -0700 Date: Tue, 24 Sep 1996 09:30:24 -0700 From: Jim Shankland Message-Id: <199609241630.JAA13814@saguaro.flyingfox.com> To: dg@root.com, jas@flyingfox.COM Subject: Re: mb_map full Cc: freebsd-isp@freebsd.org, robseco@wizard.teksupport.net.au Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > The kmem_map full panic was the result of a mis-calculation of > the size of the map in 2.1R. The calculation didn't account for > the mb_map being a submap of it, and thus large mb_maps would > leave little space left over for the [much more important] > kmem_map. This was fixed in post-2.1 with the following commit: [ ... ] Thanks for the information. But does making the kmem_map larger, as you described, eliminate the panic, or just make it less likely? In other words, is the kmem_map now sized so that it can never possibly fill up? mbufs, for example (not clusters), still come out of the kmem_map, and I don't know of any a priori upper bound on the number of mbufs that can be consumed. It still seems that an unluckily timed call to malloc (resulting in a call to kmem_malloc) with WAITOK can trigger a panic. I will happily stand corrected if any of this is not right. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-isp Tue Sep 24 09:56:42 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA27770 for isp-outgoing; Tue, 24 Sep 1996 09:56:42 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA27716 for ; Tue, 24 Sep 1996 09:56:32 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA06476; Tue, 24 Sep 1996 11:55:23 -0500 From: Joe Greco Message-Id: <199609241655.LAA06476@brasil.moneng.mei.com> Subject: Re: Thoughts on a news server cluster To: taob@io.org Date: Tue, 24 Sep 1996 11:55:23 -0500 (CDT) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: from "Brian Tao" at Sep 24, 96 12:06:11 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Mon, 23 Sep 1996, Joe Greco wrote: > > > > You get more concurrency if you use ccd too :-) > > True enough, but I didn't feel ccd was stable enough when I first > built our news server (late last year). I've been using it for about that long without many problems... but it was certainly rough around the edges at first. > > If nothing else, you can get a "SCSI-SCSI" translator (made by Mylex > > and others) where you just provide a fast/wide SCSI adaptor (2940, > > etc) and let the black box handle the RAID aspects. > > Good news... Open Storage says they will have a 5x4GB CRD-5300 > (might be a bit off on the model number) with 64MB cache available for > me in the next couple of days. The PPro systems are arriving this > afternoon, and I'm going to order a bunch of 2GB drives in a rackmount > chassis for next week. That will give me one system with a single F/W > drive, a ccd of 2GB drives, a Streamlogic hardware RAID and a CMD > hardware RAID for benchmark comparisons. The bits will be flying. ;-) Ahhh nice :-) > > Support is probably going to appear for several host adapter RAID > > solutions in the not too distant future, if I believe what people are > > telling me :-) > > Anything happening with the effort to pool some money together to > pay a programmer to accelerate his port the DPT drivers? I *might* be > able to convince the company to toss in some money towards such an > effort. I had heard a few various words from people, but IIRC somebody already "almost" has a DPT driver sitting on a back burner. Rod Grimes might have said something about looking at this - but you will have to ask him. > > You do NOT want to NFS mount!!! I have done it. If you have the I/O > > bandwidth and CPU (but not the RAM) to spare on a machine, it may be a > > worthwhile option... but the tax on the host is high. And you take a > > major reliability hit if that host goes down. > > I'm trying to do a simple sort of cost-benefit analysis. Two F/W > controllers and level 5 RAID with 25GB of usuable capacity costs in > the $25000 range. Per machine. For that kind of money, I'm > definitely willing to give NFS-mounted reader servers a try. J****! Let me build this in my mind quickly... Pentium 133 with ASUS P/E-XXXX????? MB $ 800 3 x NCR 810, 1 x SMC EtherPower 10/100 $ 320 192MB RAM $1200 6 x ST32550N $4100 4 x ST31055N $1200 2 x ST15150N $1850 Ext enclosures (3) $ 660 ----- $10130 That gives you 24GB usable _local_ disk capacity and additional I/O bandwidth on top of it... and you can build three with your $25000 plus some change, considering that you can get quantity pricing on a purchase of so many drives. And you get _complete_ redundancy rather than only disk subsystem redundancy. That is the part that gets me excited. > > It gives me 9 days retention on most stuff, 12 on alt, 2 on > > alt.binaries. It supports 150 users and _flies_, and even at 200 the > > performance is "acceptable" (but starts to degrade.. pretty much > > simultaneously RAM and I/O bandwidth start to dry up). > > The only performance problem I'm seeing is long delays or timeouts > when attempting to open an NNRP session. Once I'm in, the server is > niec and fast. I haven't tried anything special with starting > in.nnrpd's out of inetd and running innd on a different port, etc. It > seems to be related to the number of incoming innxmit connections. Yes. I deal with it by not launching nnrp's out of innd. I have something (local hackery) called "connectd" which is like a nnrp inetd, but has additional intelligence and allows me to limit the number of simultaneous connections or the respawn rate from a particular host. We have wankers around here who like running crap like NewsBin95. You also have windows of unavailability when the server is running news.daily and doing a renumber, etc. etc... spawning out of innd is not ideal. > > PPro200? Heavy iron for news... what exactly are you doing with all > > that horsepower... :-) > > They were roughly same price as Pentium 200's (a couple hundred > dollars difference). Maybe I'll start playing with on-the-fly > compression of news articles. ;-) Why not compute a few prime numbers too. ;-) > > That is one way to handle it, but I find that running XREPLIC off of > > the feeds system is perfectly acceptable... if I was going to have a > > separate "reader" fan-out machine I would probably STILL run it as an > > XREPLIC slave from the feeder machine... convenience. > > I don't want to "lock" myself into using XREPLIC though. If the > main feeder blows up and I have to newfs the spool, it'll take extra > work to resync those article numbers. If I just treat the feeder and Why? Grab the active off of a slave - if you are really anal, grab the active off all the slaves and write a little perl script to find the max for each group (just in case the slaves were a tad out of sync). That is a bit of work, I agree, but not hard. > the primary reader machine as entirely autonomous servers, something > that goes wrong with one is less likely to affect the other. Also, > isn't slave mode required for XREPLIC? Yes. > If the feeder server is > unavailable, none of the reader machines will be able to post. A qualified "Yes." You have the same problem no matter what you do, since INN has a synchronous posting paradigm that in my opinion bites the big one. I got exasperated and did something different. I developed a smart spooling system to deal with it. Now people can "post" even if the master and all the other slaves are dead. At the same time I took the opportunity to add a comprehensive posting accounting system that records whatever the hell gets posted. It's been useful several times already... % cd /var/log/news/logposts/posts/idiot.user@execpc.com/ % grep "^Message-ID: " * | awk '{print $2}' > /tmp/cancelme % spamcancel /tmp/cancelme :-) MUCH easier than in the old days... digging through logs, etc. > I've > not played with XREPLIC before, so my understanding may be off. XREPLIC is a form of mildly tying your hands. On the other hand, it keeps your machines in sync! Which is what an ISP needs. > > I don't know, I would think that I would start seeing some I/O > > contention with just one machine.. > > I don't think we're going to hit 1000 simultaneous readers at this > POP for a while yet. It will be a gradual curve up, so any > anticipated I/O bottlenecks can be headed off before they become a > problem. Do we have any kernel optimizations yet for PPro memory- > intensive operations? Dunno > > And I have not seen any basis for supporting that many readers on a > > single machine.. how big is your active file? What does "top"'s > > output look like on one of your readers? Enquiring minds want to know :-) > > It's a pretty small active file, just under 9000 groups (407187 > bytes). 'top' looks like this: Ahhh that's why. I have 25000+++ with well over 1MB size. > load averages: 0.36, 0.42, 0.41 11:52:58 > 109 processes: 1 running, 118 sleeping > Cpu states: 2.7% user, 1.5% nice, 14.2% system, 2.3% interrupt, 79.2% idle > Mem: 82M Active, 6152K Inact, 20M Wired, 19M Cache, 7785K Buf, 176K Free > Swap: 262M Total, 8336K Used, 254M Free, 3% Inuse > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 27230 news -6 0 24M 24M biowai 95:05 13.08% 11.02% innd.nodebug > 27238 root 29 0 352K 808K RUN 0:00 3.15% 0.57% top > 26658 news 2 4 316K 708K select 0:01 0.38% 0.38% in.nnrpd > 25061 news 2 0 220K 352K sbwait 0:22 0.31% 0.31% innxmit > 27200 news 2 4 292K 868K sbwait 0:00 0.23% 0.23% in.nnrpd > 27235 news 2 0 292K 992K select 0:00 0.38% 0.19% in.nnrpd > 27233 news -6 0 152K 484K piperd 0:00 0.20% 0.15% overchan > 27150 news 2 4 288K 728K sbwait 0:00 0.08% 0.08% in.nnrpd > 27190 news 2 4 284K 692K sbwait 0:00 0.08% 0.08% in.nnrpd > 26803 news 2 4 292K 732K sbwait 0:00 0.04% 0.04% in.nnrpd > 26480 news 2 0 448K 548K select 0:04 0.04% 0.04% innxmit > 23024 news 2 0 220K 308K sbwait 0:31 0.04% 0.04% innxmit > [...] Looks more like load averages: 1.48, 0.89, 0.60 11:40:14 96 processes: 2 running, 94 sleeping Cpu states: 1.8% user, 15.5% nice, 24.1% system, 2.5% interrupt, 56.1% idle Mem: 92M Active, 396K Inact, 19M Wired, 71M Cache, 5304K Buf, 260K Free Swap: 369M Total, 40M Used, 329M Free, 11% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 24372 news 74 4 47M 21M RUN 727:22 27.89% 27.89% innd 6228 news 2 0 1048K 2368K select 0:02 1.64% 1.64% in.nnrpd 6805 news 2 0 1080K 2384K select 0:00 2.02% 1.07% in.nnrpd 6801 news 2 0 1032K 2340K select 0:01 1.14% 0.99% in.nnrpd 6812 news 2 0 1028K 2324K select 0:00 1.89% 0.95% in.nnrpd 6633 news 2 0 1020K 2332K netio 0:03 0.92% 0.92% in.nnrpd here, see the difference in size... :-( > Assuming 32MB for kernel and OS stuff, 32MB for innd, 150MB for 500 > readers and no feeds, that still leaves ~40MB for disk cache and other > processes (like expires) on a 256MB machine. Must be nice to have a small active file. ;-) ... JG From owner-freebsd-isp Tue Sep 24 15:24:16 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA22821 for isp-outgoing; Tue, 24 Sep 1996 15:24:16 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA22713 for ; Tue, 24 Sep 1996 15:24:08 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id SAA12795; Tue, 24 Sep 1996 18:22:44 -0400 (EDT) Date: Tue, 24 Sep 1996 18:22:44 -0400 (EDT) From: Brian Tao To: Joe Greco cc: freebsd-isp@FreeBSD.ORG Subject: Re: Thoughts on a news server cluster In-Reply-To: <199609241655.LAA06476@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 24 Sep 1996, Joe Greco wrote: > > J****! > > Let me build this in my mind quickly... > > Pentium 133 with ASUS P/E-XXXX????? MB $ 800 > 3 x NCR 810, 1 x SMC EtherPower 10/100 $ 320 > 192MB RAM $1200 > 6 x ST32550N $4100 > 4 x ST31055N $1200 > 2 x ST15150N $1850 > Ext enclosures (3) $ 660 > ----- > $10130 Yep, this is the cost breakdown (in Cdn $... divide by 1.4 or so to get US bucks): 19" rackmount drive chassis $1275 RAIDION Gandiva controller $4000 8 x 2.1GB drive modules $10200 -------------------------------------------- 1 RAID system $15475 Add $400 for an Adaptec 2940UW controller, then multiply by two. Compare that to $3605 for a PPro200, 256K L1 and 512K L2, ASUS P/I-P6NP5 motherboard, 128MB of EDO, AHA-2940UW, Seagate ST31230W 1GB wide drive and SMC EtherPower 10/100Mbps. > That gives you 24GB usable _local_ disk capacity and additional > I/O bandwidth on top of it... and you can build three with your > $25000 plus some change, considering that you can get quantity > pricing on a purchase of so many drives. > > And you get _complete_ redundancy rather than only disk subsystem > redundancy. That is the part that gets me excited. True enough. I would like to have the rackmount chassis and slide-in drive sleds to minimize downtime if I do have to replace a drive. An 8-bay rack chassis from CRU is around $1400 I think. It includes the sleds, a second power supply and an external 68-pin wide SCSI connector. That would knock the price of a 14x2GB subsystem down to around $16000. More points to ponder... :) > Yes. I deal with it by not launching nnrp's out of innd. I have > something (local hackery) called "connectd" I saw some early source code that you (at least I think it was you... I might be confusing you with T. W. Wells) had posted to news.software.nntp. I haven't actually done anything with it since I didn't have another machine on which to experiment. > You also have windows of unavailability when the server is running > news.daily and doing a renumber, etc. etc... spawning out of innd is > not ideal. No, the monolithic server approach was a good idea back when news volumes were small, but now there's too much going on for a non- threaded process to handle. All innd should be is a glorified inetd that does some coordination between feeds, but otherwise fire off new connections as quickly as possible. > Why not compute a few prime numbers too. ;-) It's high time I ran Crack on the passwd file too. ;-) > Grab the active off of a slave - if you are really anal, grab the > active off all the slaves and write a little perl script to find the > max for each group (just in case the slaves were a tad out of sync). > That is a bit of work, I agree, but not hard. Hrm, I'm still not so sure... XREPLIC seems like a big kludge to me, and I need to depend on the master server anyway if I want to be able to post. If I run NFS between the readers and have them all post back to the primary reader, it at least insulates them from badness happening on the feeder server. There is still a point of failure on the primary reader, but that's somewhat better than having everything depend on a single server being available 100% of the time. > A qualified "Yes." You have the same problem no matter what you do, > since INN has a synchronous posting paradigm that in my opinion bites > the big one. Something that could quickly batch incoming posts and then inject them into the news stream a la rnews would be sufficient unless you were concerned with sub-minute propagation of articles from your site. > I got exasperated and did something different. I developed a smart > spooling system to deal with it. Now people can "post" even if the > master and all the other slaves are dead. At the same time I took the > opportunity to add a comprehensive posting accounting system that > records whatever the hell gets posted. It's been useful several times > already... I think your work would make a *fine* contribution to the INN contrib/ directory... ;-) > XREPLIC is a form of mildly tying your hands. On the other hand, it > keeps your machines in sync! Which is what an ISP needs. Keeping multiple reader servers in sync is definitely a must, but I've heard about an equal number of opinions favouring NFS or XREPLIC. NFS is cheaper, your articles by definition are "in sync", you don't have to run an innd process for each server, but it sucks up I/O and CPU resources. XREPLIC requires local disks, can keep articles in sync, hogs more RAM because of innd, but offers better redundancy (at least for reading). > Must be nice to have a small active file. ;-) Back when I kept detailed readership stats, I found that over a period of one week, only ~4500 groups had at least one access. Most of the readership was in 50 to 60 of the alt.binaries and alt.sex groups. Over the past year, I've added a couple hundred groups on user request, and people seem pretty happy with that arrangement. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-isp Tue Sep 24 22:30:56 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA03828 for isp-outgoing; Tue, 24 Sep 1996 22:30:56 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA03803 for ; Tue, 24 Sep 1996 22:30:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id WAA05649; Tue, 24 Sep 1996 22:31:57 -0700 (PDT) Message-Id: <199609250531.WAA05649@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Jim Shankland cc: freebsd-isp@freebsd.org, robseco@wizard.teksupport.net.au Subject: Re: mb_map full In-reply-to: Your message of "Tue, 24 Sep 1996 09:30:24 PDT." <199609241630.JAA13814@saguaro.flyingfox.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 24 Sep 1996 22:31:57 -0700 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >David Greenman writes: > >> The kmem_map full panic was the result of a mis-calculation of >> the size of the map in 2.1R. The calculation didn't account for >> the mb_map being a submap of it, and thus large mb_maps would >> leave little space left over for the [much more important] >> kmem_map. This was fixed in post-2.1 with the following commit: >[ ... ] > >Thanks for the information. But does making the kmem_map larger, >as you described, eliminate the panic, or just make it less Yes, it eliminates the panic. >likely? In other words, is the kmem_map now sized so that it >can never possibly fill up? mbufs, for example (not clusters), >still come out of the kmem_map, and I don't know of any a priori >upper bound on the number of mbufs that can be consumed. It Yes, there is a limit on the allocations that will prevent them from consuming the entire map. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-isp Wed Sep 25 00:20:17 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA29201 for isp-outgoing; Wed, 25 Sep 1996 00:20:17 -0700 (PDT) Received: from alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA29157; Wed, 25 Sep 1996 00:20:12 -0700 (PDT) Received: from hmmm.alaska.net by alaska.net (5.x/SMI-SVR4) id AA02387; Tue, 24 Sep 1996 23:05:02 -0800 Date: Wed, 25 Sep 1996 07:06:20 +0000 () From: hmmm To: freebsd-questions Cc: freebsd-hackers , freebsd-isp Subject: unsubscribe Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-isp Wed Sep 25 03:42:18 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA10171 for isp-outgoing; Wed, 25 Sep 1996 03:42:18 -0700 (PDT) Received: from wgserv.cpl.net ([206.171.202.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA10126 for ; Wed, 25 Sep 1996 03:42:11 -0700 (PDT) Received: from [206.171.202.66] by cpl.net id 198e0.wrk; Wed, 25 Sep 1996 03:12:28 PST Message-Id: <1.5.4.32.19960925100730.00663e3c@cpl.net> X-Sender: avatar@cpl.net X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 25 Sep 1996 03:07:30 -0700 To: isp@freebsd.org From: Shawn Ramsey Subject: Dialup Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know of any books, or anything, that explains how to setup dialup with FreeBSD 2.1.x ?? Ive looked at the handbook, but it is for 1.x and doesnt seem to be much help... From owner-freebsd-isp Wed Sep 25 11:40:28 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA07872 for isp-outgoing; Wed, 25 Sep 1996 11:40:28 -0700 (PDT) Received: from house.multinet.net (house.multinet.net [204.138.173.37]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA07733 for ; Wed, 25 Sep 1996 11:40:07 -0700 (PDT) Received: (from graydon@localhost) by house.multinet.net (8.6.12/8.6.12) id OAA01079; Wed, 25 Sep 1996 14:39:49 -0400 Date: Wed, 25 Sep 1996 14:39:49 -0400 (EDT) From: Graydon Hoare To: freebsd-isp@freebsd.org Subject: Ascend access switches? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone used one of these ascend max 4000ex's? My boss just handed me literature. they look a lot like the telebit mica machines. I see lots of people discussing their portmasters -- anyone tried anything else? -graydon From owner-freebsd-isp Wed Sep 25 14:08:32 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28458 for isp-outgoing; Wed, 25 Sep 1996 14:08:32 -0700 (PDT) Received: from bitbucket.edmweb.com (bitbucket.edmweb.com [204.244.190.9]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA28401 for ; Wed, 25 Sep 1996 14:08:24 -0700 (PDT) Received: (from steve@localhost) by bitbucket.edmweb.com (8.6.12/8.6.12) id OAA00294; Wed, 25 Sep 1996 14:08:16 -0700 Date: Wed, 25 Sep 1996 14:08:12 -0700 (PDT) From: Steve Reid To: freebsd-isp@freebsd.org Subject: Eudora connecting to port 106? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk One of my users has an oldish version of Eudora, 16-bit I think. He can't access our mail server. tcpdump shows that he's trying to connect to port 106, instead of the usual pop2/pop3 ports. I tried putting popper on port 106 but it still didn't work. Has anyone else seen this? What am I supposed to put on port 106? ===================================================================== | Steve Reid - SysAdmin & Pres, EDM Web (http://www.edmweb.com/) | | Email: steve@edmweb.com Home Page: http://www.edmweb.com/steve/ | | PGP (2048/9F317269) Fingerprint: 11C89D1CD67287E68C09EC52443F8830 | | -- Disclaimer: JMHO, YMMV, TANSTAAFL, IANAL. -- | ===================================================================:) From owner-freebsd-isp Wed Sep 25 14:27:10 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA06565 for isp-outgoing; Wed, 25 Sep 1996 14:27:10 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA06525 for ; Wed, 25 Sep 1996 14:27:05 -0700 (PDT) Received: from noc.msc.edu by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0v61Tv-00091xC; Wed, 25 Sep 96 14:26 PDT Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA05197; Wed, 25 Sep 96 16:23:05 -0500 Received: from fergus-17.dialup.prtel.com by uc.msc.edu (5.65/MSC/v3.0z(901212)) id AA15295; Wed, 25 Sep 96 16:23:03 -0500 Received: (from alk@localhost) by compound.Think.COM (8.7.6/8.7.3) id QAA26745; Wed, 25 Sep 1996 16:24:48 -0500 (CDT) Date: Wed, 25 Sep 1996 16:24:48 -0500 (CDT) From: Tony Kimball Message-Id: <199609252124.QAA26745@compound.Think.COM> To: admin@multinet.net Cc: freebsd-isp@FreeBSD.org Subject: Ascend access switches? References: Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Quoth Graydon Hoare on Wed, 25 September: : Anyone used one of these ascend max 4000ex's? : My boss just handed me literature. they look a lot like the telebit mica : machines. I see lots of people discussing their portmasters -- anyone : tried anything else? PortMaster is a trademark of Livingston, a competitor to Ascend. There are PortMaster terminal servers (POTS/ISDN) and (integrated) routers. I have used neither, but will say that the word of mouth on Ascend products is much better than Livingston products, if you can stomach their licensing terms, which I cannot. From owner-freebsd-isp Wed Sep 25 15:02:42 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA24352 for isp-outgoing; Wed, 25 Sep 1996 15:02:42 -0700 (PDT) Received: from adsight.com (adsight.com [207.86.2.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA24316 for ; Wed, 25 Sep 1996 15:02:37 -0700 (PDT) Received: (from webadmin@localhost) by adsight.com (8.7.5/8.6.12) id RAA00431; Wed, 25 Sep 1996 17:58:35 -0400 (EDT) Date: Wed, 25 Sep 1996 17:58:35 -0400 (EDT) From: Sam Magee To: freebsd-isp@FreeBSD.org Subject: uptime probs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Anyone have problems with their webserver getting sluggish after x number of days. It seems that after 2 to 14 days, things start to slow down, and if I reboot the system, it clears up. I'm using 2.1.5R with 64Megs ram, and have only web traffic (and not that much right now, so there's really no reason for any congestion). The web server is Apache 1.0.5. Still using the GENERIC kernel -- could this be the problem? Thanks Sam From owner-freebsd-isp Wed Sep 25 16:26:26 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA03970 for isp-outgoing; Wed, 25 Sep 1996 16:26:26 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA03928 for ; Wed, 25 Sep 1996 16:26:18 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id JAA18010; Thu, 26 Sep 1996 09:26:16 +1000 (EST) Date: Thu, 26 Sep 1996 09:26:14 +1000 (EST) From: "Daniel O'Callaghan" To: Steve Reid cc: freebsd-isp@FreeBSD.org Subject: Re: Eudora connecting to port 106? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Sep 1996, Steve Reid wrote: > One of my users has an oldish version of Eudora, 16-bit I think. He can't > access our mail server. tcpdump shows that he's trying to connect to port > 106, instead of the usual pop2/pop3 ports. I tried putting popper on port > 106 but it still didn't work. > > Has anyone else seen this? What am I supposed to put on port 106? 106 is where poppassd goes. Danny From owner-freebsd-isp Wed Sep 25 16:53:09 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA15069 for isp-outgoing; Wed, 25 Sep 1996 16:53:09 -0700 (PDT) Received: from radius.vector.net (cbw@radius.vector.net [207.22.177.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA14976 for ; Wed, 25 Sep 1996 16:52:56 -0700 (PDT) Received: from localhost (cbw@localhost) by radius.vector.net (8.6.12/8.6.6) with SMTP id TAA14013; Wed, 25 Sep 1996 19:51:29 -0400 Date: Wed, 25 Sep 1996 19:51:29 -0400 (EDT) From: "Chris B. Wilson" To: Tony Kimball cc: admin@multinet.net, freebsd-isp@freebsd.org Subject: Re: Ascend access switches? In-Reply-To: <199609252124.QAA26745@compound.Think.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Livingston has just announced the latest product in their PortMaster line, the Portmaster 3. It integrates ISDN and Analog connections into the same box, in the fassion of the MAX. However, Livingston's solution is *much* more affordable. A fully loaded 48-port PM3 which will support 48 B channels or 48 33.6k digital modem connections (or any combination inbetween) is only around $350/port. That is *very* impressive, since if you considered the previous alternatives. $350/port is a damn good price even for analog dial-up (managed rack mount). Plus having 48 ports in half the space of a PM2E is pretty impressive. I've been using Livingston for quite a while now, and have been very happy with their products, support, and people. Chris On Wed, 25 Sep 1996, Tony Kimball wrote: > Quoth Graydon Hoare on Wed, 25 September: > : Anyone used one of these ascend max 4000ex's? > : My boss just handed me literature. they look a lot like the telebit mica > : machines. I see lots of people discussing their portmasters -- anyone > : tried anything else? > > PortMaster is a trademark of Livingston, a competitor to Ascend. > There are PortMaster terminal servers (POTS/ISDN) and (integrated) > routers. I have used neither, but will say that the word of mouth on > Ascend products is much better than Livingston products, if you can > stomach their licensing terms, which I cannot. > > > > // Chris Wilson, Gateway Telecommunications, Inc. | Ofc: 352.375.8658 // // http://www.vector.net/~cbw cbw@vector.net | Pgr: 352.412.4341 // // VectorNet - Quality Internet in Gainesville, Florida | Fax: 352.376.8353 // From owner-freebsd-isp Wed Sep 25 16:53:16 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA15159 for isp-outgoing; Wed, 25 Sep 1996 16:53:16 -0700 (PDT) Received: from ng.netgate.net (narf@ng.netgate.net [204.145.147.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA15107 for ; Wed, 25 Sep 1996 16:53:10 -0700 (PDT) Received: (from narf@localhost) by ng.netgate.net (8.7.4/8.6.9) id QAA04008; Wed, 25 Sep 1996 16:59:47 -0700 (PDT) Date: Wed, 25 Sep 1996 16:59:47 -0700 (PDT) From: Matt Clark To: Steve Reid cc: freebsd-isp@FreeBSD.org Subject: Re: Eudora connecting to port 106? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk 106 Is The Password Changing Port --matt Clark On Wed, 25 Sep 1996, Steve Reid wrote: > One of my users has an oldish version of Eudora, 16-bit I think. He can't > access our mail server. tcpdump shows that he's trying to connect to port > 106, instead of the usual pop2/pop3 ports. I tried putting popper on port > 106 but it still didn't work. > > Has anyone else seen this? What am I supposed to put on port 106? > > > ===================================================================== > | Steve Reid - SysAdmin & Pres, EDM Web (http://www.edmweb.com/) | > | Email: steve@edmweb.com Home Page: http://www.edmweb.com/steve/ | > | PGP (2048/9F317269) Fingerprint: 11C89D1CD67287E68C09EC52443F8830 | > | -- Disclaimer: JMHO, YMMV, TANSTAAFL, IANAL. -- | > ===================================================================:) > > From owner-freebsd-isp Wed Sep 25 16:53:39 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA15356 for isp-outgoing; Wed, 25 Sep 1996 16:53:39 -0700 (PDT) Received: from DNS.Lamb.net (root@DNS.Lamb.net [206.169.44.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA15312 for ; Wed, 25 Sep 1996 16:53:29 -0700 (PDT) Received: from Gatekeeper.Lamb.net (ulf@Gatekeeper.Lamb.net [206.169.44.2]) by DNS.Lamb.net (8.7.6/8.7.3) with ESMTP id QAA01645; Wed, 25 Sep 1996 16:55:32 -0700 (PDT) Received: (from ulf@localhost) by Gatekeeper.Lamb.net (8.7.6/8.7.6) id QAA03051; Wed, 25 Sep 1996 16:54:23 -0700 (PDT) From: Ulf Zimmermann Message-Id: <199609252354.QAA03051@Gatekeeper.Lamb.net> Subject: Re: uptime probs To: webadmin@adsight.com (Sam Magee) Date: Wed, 25 Sep 1996 16:54:23 -0700 (PDT) Cc: freebsd-isp@freebsd.org In-Reply-To: from Sam Magee at "Sep 25, 96 05:58:35 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Anyone have problems with their webserver getting sluggish after > x number of days. It seems that after 2 to 14 days, things start > to slow down, and if I reboot the system, it clears up. > I'm using 2.1.5R with 64Megs ram, and have only web traffic (and not > that much right now, so there's really no reason for any congestion). > The web server is Apache 1.0.5. > Still using the GENERIC kernel -- could this be the problem? > > Thanks > > Sam > > As first try I would upgrade to apache 1.1.1 and maybe also build a kernel specific for the hardware in that machine. Ulf. -------------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 Lamb Art Internet Services | http://www.Lamb.net/ | http://www.Alameda.net From owner-freebsd-isp Wed Sep 25 22:44:16 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA21068 for isp-outgoing; Wed, 25 Sep 1996 22:44:16 -0700 (PDT) Received: from dnai.com (dnai.com [140.174.162.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA21031 for ; Wed, 25 Sep 1996 22:44:13 -0700 (PDT) Received: from mars.dnai.com (mars.dnai.com [140.174.162.14]) by dnai.com (8.7.5/8.7.3) with SMTP id WAA23305; Wed, 25 Sep 1996 22:43:08 -0700 (PDT) Date: Wed, 25 Sep 1996 22:43:08 -0700 (PDT) From: Dror Matalon To: "Chris B. Wilson" cc: freebsd-isp@freebsd.org Subject: Re: Ascend access switches? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We use both the Max and the old portmasters (pm2e). The Max 4000 for ISDN and the portmaster in conjunction with Microcom Racks for modems. The 4000 is wonderful since you get a device that's smaller than a portmaster that handles up to 95 B channels. I wish Ascend's QA department would be a little more careful with the numerous releases they issue so that we don't need to keep updating as often as we do. Other than that the Max is a nice Box. The old portmasters are old workhorses, they handle up to 30 28.8/33.6 modems and they just work and work. On Wed, 25 Sep 1996, Chris B. Wilson wrote: > Livingston has just announced the latest product in their PortMaster line, > the Portmaster 3. It integrates ISDN and Analog connections into the same > box, in the fassion of the MAX. However, Livingston's solution is *much* > more affordable. A fully loaded 48-port PM3 which will support 48 B > channels or 48 33.6k digital modem connections (or any combination > inbetween) is only around $350/port. > > That is *very* impressive, since if you considered the previous > alternatives. $350/port is a damn good price even for analog dial-up > (managed rack mount). Plus having 48 ports in half the space of a PM2E is > pretty impressive. As far as I'm concerned this is vapor-ware. It's not shipping, so it might be here in a month, or not. Please notice also that Ascend has a deal for ISPs, a Max4000 with 48 digital modems for 22,500 or $468 ports. Since you get 45 more B channels, this is a great deal if you do both ISDN and modems. > > I've been using Livingston for quite a while now, and have been very happy > with their products, support, and people. > > Chris > > On Wed, 25 Sep 1996, Tony Kimball wrote: > > > Quoth Graydon Hoare on Wed, 25 September: > > : Anyone used one of these ascend max 4000ex's? > > : My boss just handed me literature. they look a lot like the telebit mica > > : machines. I see lots of people discussing their portmasters -- anyone > > : tried anything else? > > > > PortMaster is a trademark of Livingston, a competitor to Ascend. > > There are PortMaster terminal servers (POTS/ISDN) and (integrated) > > routers. I have used neither, but will say that the word of mouth on > > Ascend products is much better than Livingston products, if you can > > stomach their licensing terms, which I cannot. > > > > > > > > > > > // Chris Wilson, Gateway Telecommunications, Inc. | Ofc: 352.375.8658 // > // http://www.vector.net/~cbw cbw@vector.net | Pgr: 352.412.4341 // > // VectorNet - Quality Internet in Gainesville, Florida | Fax: 352.376.8353 // > > Dror Matalon Voice: 510 649-6110 Direct Network Access Fax: 510 649-7130 2039 Shattuck Avenue Modem: 510 649-6116 Berkeley, CA 94704 Email: dror@dnai.com From owner-freebsd-isp Wed Sep 25 22:46:23 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA22494 for isp-outgoing; Wed, 25 Sep 1996 22:46:23 -0700 (PDT) Received: from dnai.com (dnai.com [140.174.162.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA22468 for ; Wed, 25 Sep 1996 22:46:21 -0700 (PDT) Received: from mars.dnai.com (mars.dnai.com [140.174.162.14]) by dnai.com (8.7.5/8.7.3) with SMTP id WAA23423; Wed, 25 Sep 1996 22:45:13 -0700 (PDT) Date: Wed, 25 Sep 1996 22:45:13 -0700 (PDT) From: Dror Matalon To: Sam Magee cc: freebsd-isp@FreeBSD.org Subject: Re: uptime probs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Sep 1996, Sam Magee wrote: > Anyone have problems with their webserver getting sluggish after > x number of days. It seems that after 2 to 14 days, things start > to slow down, and if I reboot the system, it clears up. > I'm using 2.1.5R with 64Megs ram, and have only web traffic (and not > that much right now, so there's really no reason for any congestion). > The web server is Apache 1.0.5. > Still using the GENERIC kernel -- could this be the problem? I would also do a netstat -m to see that mbufs are not used up. This used to be a problem with our Web server until we increased the mbuf allocation to 4Megs. > > Thanks > > Sam > > Dror Matalon Voice: 510 649-6110 Direct Network Access Fax: 510 649-7130 2039 Shattuck Avenue Modem: 510 649-6116 Berkeley, CA 94704 Email: dror@dnai.com From owner-freebsd-isp Thu Sep 26 07:48:13 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA21592 for isp-outgoing; Thu, 26 Sep 1996 07:48:13 -0700 (PDT) Received: from challenge.com (nomad.challenge.com [206.12.153.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA21519 for ; Thu, 26 Sep 1996 07:48:03 -0700 (PDT) Received: from [206.12.153.100] by challenge.com with smtp (Smail3.1.29.1 #3) id m0v6HjH-003kMyC; Thu, 26 Sep 96 07:47 PDT Message-Id: To: "isp@FreeBSD.Org" Date: Thu, 26 Sep 96 07:48:10 -0500 From: Doug Woodward X-Mailer: E-Mail Connection v3.1 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -- [ From: Doug Woodward * EMC.Ver #3.1 ] -- unscribe ips@FreeBSD.Org From owner-freebsd-isp Thu Sep 26 07:50:11 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA22561 for isp-outgoing; Thu, 26 Sep 1996 07:50:11 -0700 (PDT) Received: from challenge.com (nomad.challenge.com [206.12.153.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA22528 for ; Thu, 26 Sep 1996 07:50:03 -0700 (PDT) Received: from [206.12.153.100] by challenge.com with smtp (Smail3.1.29.1 #3) id m0v6HlJ-003kMyC; Thu, 26 Sep 96 07:50 PDT Message-Id: To: "isp@FreeBSD.Org" Date: Thu, 26 Sep 96 07:50:16 -0500 From: Doug Woodward X-Mailer: E-Mail Connection v3.1 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -- [ From: Doug Woodward * EMC.Ver #3.1 ] -- unsubscribe isp@FreeBSD.org From owner-freebsd-isp Thu Sep 26 10:22:17 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA16297 for isp-outgoing; Thu, 26 Sep 1996 10:22:17 -0700 (PDT) Received: from brutus.transport.com (root@transport.com [204.119.17.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA16266 for ; Thu, 26 Sep 1996 10:22:14 -0700 (PDT) Received: from tod.transport.com (tod.transport.com [204.119.17.84]) by brutus.transport.com (8.7.3/8.6.10) with SMTP id KAA12357 for ; Thu, 26 Sep 1996 10:22:00 -0700 Message-Id: <199609261722.KAA12357@brutus.transport.com> X-Sender: tod@transport.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 26 Sep 1996 10:26:03 -0800 To: freebsd-isp@freebsd.org From: tod@TRANSPORT.COM (Tod Allen) Subject: SCO Sendmail Solution??? Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >X-POP3-Rcpt: tod@brutus >Return-Path: tonys@transport.com >Date: Thu, 26 Sep 1996 09:01:08 -0700 >X-Sender: tonys@transport.com >To: inet-access@earth.com >From: tonys@transport.com (Tony Schwartz) >Subject: SCO Sendmail Solution??? > > >We are into a project that is causing us severe grief. We have a client >running SCO/Unix that needs a good sendmail solution. We have a sendmail >program working on it but not a local delivery agent. > >Does anyone have a solution???? I am urgent for a solution so please email >any thoughts. > >Tony >************************************************************************** >Tony Schwartz, President Transport Logic >Transport Logic 50 SW 2nd Ave., Suite 510 Portland, OR 97204 >Phone: (503) 243-1940 Fax (503) 243-2792 >************************************************************************** > > ************************************************************************** Tod Allen tod@transport.com WWW: http://www.transport.com Transport Logic 50 SW 2nd Ave., Suite 510, Portland, OR 97204 Portland:(503) 243-1940, Fax (503) 243-2792, Bend:(541) 317-0400, Salem:(503) 588-7332, Vancouver:(360) 693-9090, Seaside:(503) 738-3844 "The Northwest's Premier Internet Services Provider" ************************************************************************** From owner-freebsd-isp Thu Sep 26 10:46:43 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA02832 for isp-outgoing; Thu, 26 Sep 1996 10:46:43 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA02779 for ; Thu, 26 Sep 1996 10:46:38 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id TAA23693 for ; Thu, 26 Sep 1996 19:44:14 +0200 Message-Id: <199609261744.TAA23693@login.bigblue.no> From: "Frode Nordahl" To: "isp@FreeBSD.org" Date: Thu, 26 Sep 96 19:43:16 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: wu-ftpd and multi-IP patch problem?? Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi! I just got some complaints about files getting corrupted when our users use our FTP server wich is wu-ftpd-2.4(5) with the multi-ip patch applied. I did this test. Uploaded nsos21a.zip, downloaded the file again and ran a compare. This is the output: Sammenlikner filene D:nsos21a.zip og D:..\nsos21a.zip. Sammenlikningsfeil i relativ posisjon 19FFE (Error comparing in possition 19FFE) Avvikende byte i fil 1 = 46 (Diff byte file 1 = 46) Avvikende byte i fil 2 = 20 (Diff byte file 2 = 20) Sammenlikningsfeil i relativ posisjon 19FFF (Error comparing in possition 19FFF) Avvikende byte i fil 1 = BF (Diff byte file 1 = BF) Avvikende byte i fil 2 = AF (Diff byte file 2 = AF) (Sorry about it being in norwegian :) ) Anyone else has this problem?? Any sollutions? If it's not the ftpd's fault, what can be wrong? The machine is running FreeBSD 2.1.5-RELEASE. Thanks in advance for any help! --------------------------------- Frode Nordahl From owner-freebsd-isp Thu Sep 26 17:54:51 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA25938 for isp-outgoing; Thu, 26 Sep 1996 17:54:51 -0700 (PDT) Received: from localhost.dcrt.nih.gov (ost190.capecod.net [204.255.214.190]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA25879 for ; Thu, 26 Sep 1996 17:54:44 -0700 (PDT) Received: (from crtb@localhost) by localhost.dcrt.nih.gov (8.6.12/8.6.12) id UAA01174 for freebsd-isp@freebsd.org; Thu, 26 Sep 1996 20:54:35 -0400 Date: Thu, 26 Sep 1996 20:54:35 -0400 From: Chuck Message-Id: <199609270054.UAA01174@localhost.dcrt.nih.gov> To: freebsd-isp@freebsd.org Subject: Re: Eudora connecting to port 106? Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Wed, 25 Sep 1996, Steve Reid wrote: > >> One of my users has an oldish version of Eudora, 16-bit I think. He can't >> access our mail server. tcpdump shows that he's trying to connect to port >> 106, instead of the usual pop2/pop3 ports. I tried putting popper on port >> 106 but it still didn't work. >> >> Has anyone else seen this? What am I supposed to put on port 106? > >106 is where poppassd goes. > >Danny Then what is this (from 2.1R)? daisy% grep 106/ /etc/services 3com-tsmux 106/tcp 3com-tsmux 106/udp Chuck Bacon - crtb@capecod.net ABHOR SECRECY - DEFEND PRIVACY From owner-freebsd-isp Thu Sep 26 19:23:32 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA16369 for isp-outgoing; Thu, 26 Sep 1996 19:23:32 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA16322 for ; Thu, 26 Sep 1996 19:23:26 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id MAA19554; Fri, 27 Sep 1996 12:23:23 +1000 (EST) Date: Fri, 27 Sep 1996 12:23:20 +1000 (EST) From: "Daniel O'Callaghan" To: Chuck cc: freebsd-isp@FreeBSD.org Subject: Re: Eudora connecting to port 106? In-Reply-To: <199609270054.UAA01174@localhost.dcrt.nih.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 26 Sep 1996, Chuck wrote: > >On Wed, 25 Sep 1996, Steve Reid wrote: > > > > > >106 is where poppassd goes. > > Then what is this (from 2.1R)? > daisy% grep 106/ /etc/services > 3com-tsmux 106/tcp > 3com-tsmux 106/udp Something else, also on that port. But Eudora uses 106 as poppass port. Danny From owner-freebsd-isp Fri Sep 27 07:23:06 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA16168 for isp-outgoing; Fri, 27 Sep 1996 07:23:06 -0700 (PDT) Received: from mail.id.net (mail.id.net [199.125.1.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA16137 for ; Fri, 27 Sep 1996 07:23:02 -0700 (PDT) Received: from server.id.net (rls@server.id.net [199.125.1.10]) by mail.id.net (8.7.5/ID-Net) with ESMTP id KAA03154; Fri, 27 Sep 1996 10:28:12 -0400 (EDT) Received: (from rls@localhost) by server.id.net (8.7.5/8.7.3) id KAA12229; Fri, 27 Sep 1996 10:23:01 -0400 (EDT) From: Robert Shady Message-Id: <199609271423.KAA12229@server.id.net> Subject: Re: Ytalk In-Reply-To: <1.5.4.32.19960919150042.0068b63c@nwpros.com> from Rick Gray at "Sep 19, 96 10:00:42 am" To: rickg@nwpros.com (Rick Gray) Date: Fri, 27 Sep 1996 10:23:01 -0400 (EDT) Cc: isp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have downloaded Ytalk from the FBSD FTP site and when I try a make or make > install I get the error of xmkmf:not found, Error Code 2, then I get 2 > unexplained Error Code 1. Any ideas what I'm doing wrong? What is this xmkmf? You need to have X-Windows installed (XFree86) in order to make the latest version of ytalk.. Hey.. It makes sense to SOMEONE, I'm sure.. ;) Actually, there is probably some way to fanagle it to compile without it.. It sure would be nice if the ports collection contained one package for x-windows, and one package for the rest of us who run servers.. -- Rob === _/_/_/_/_/ _/_/_/_/ _/_/ _/ _/_/_/_/_/ _/_/_/_/_/ _/ _/ _/ _/_/_/ _/ _/ _/ _/_/_/_/ _/ _/_/_/_/_/ _/_/_/_/ _/ _/ _/_/_/_/_/ _/ Innovative Data Services Serving South-Eastern Michigan Internet Service Provider / Hardware Sales / Consulting Services Voice: (810)855-0404 / Fax: (810)855-3268 / Web: http://www.id.net From owner-freebsd-isp Fri Sep 27 08:47:39 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04131 for isp-outgoing; Fri, 27 Sep 1996 08:47:39 -0700 (PDT) Received: from challenge.com (nomad.challenge.com [206.12.153.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA04098 for ; Fri, 27 Sep 1996 08:47:35 -0700 (PDT) Received: from [206.12.153.100] by challenge.com with smtp (Smail3.1.29.1 #3) id m0v6f8R-003kN0C; Fri, 27 Sep 96 08:47 PDT Message-Id: To: "isp@FreeBSD.Org" Subject: unsubscribe Date: Fri, 27 Sep 96 08:47:45 -0500 From: Doug Woodward X-Mailer: E-Mail Connection v3.1 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -- [ From: Doug Woodward * EMC.Ver #3.1 ] -- unsubscribe From owner-freebsd-isp Fri Sep 27 10:45:40 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11212 for isp-outgoing; Fri, 27 Sep 1996 10:45:40 -0700 (PDT) Received: from challenge.com (nomad.challenge.com [206.12.153.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA11183 for ; Fri, 27 Sep 1996 10:45:37 -0700 (PDT) Received: from [206.12.153.100] by challenge.com with smtp (Smail3.1.29.1 #3) id m0v6gyj-003kN2C; Fri, 27 Sep 96 10:45 PDT Message-Id: To: "isp@FreeBSD.Org" Date: Fri, 27 Sep 96 10:45:50 -0500 From: Doug Woodward X-Mailer: E-Mail Connection v3.1 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -- [ From: Doug Woodward * EMC.Ver #3.1 ] -- unsubscribe freebsd-isp From owner-freebsd-isp Fri Sep 27 11:54:19 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29853 for isp-outgoing; Fri, 27 Sep 1996 11:54:19 -0700 (PDT) Received: from vis-av.com (vis-av.com [206.119.44.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA29793 for ; Fri, 27 Sep 1996 11:54:14 -0700 (PDT) Received: (from derrell@localhost) by vis-av.com (8.6.11/8.6.9) id OAA13761; Fri, 27 Sep 1996 14:52:56 -0400 Date: Fri, 27 Sep 1996 14:52:56 -0400 From: Derrell Lipman Message-Id: <199609271852.OAA13761@vis-av.com> To: Doug Woodward Cc: "isp@FreeBSD.Org" Subject: How to unsubscribe... In-Reply-To: References: Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Doug Woodward writes: > -- [ From: Doug Woodward * EMC.Ver #3.1 ] -- > > unsubscribe freebsd-isp > Sending the unsubscribe message to "isp@freebsd.org" simply posts it to all of us; it doesn't unsubscribe you. To unsubscribe from this list, send a message as follows: To: majordomo@freebsd.org Subject: unsubscribe freebsd-isp end -- Derrell -- Derrell Lipman (derrell@vis-av.com) Grumman Tiger, N28860 - Civil Air Patrol: MAWG Group 1 HQ, Operations / Cadet Programs Cadet Programs Officer, Mountain Mission Pilot, Air Ops Director, Ground Team Leader, Ground Ops Director, Mission Coordinator Trainee, Communications Unit Director, Patriot 103 From owner-freebsd-isp Fri Sep 27 12:09:54 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10777 for isp-outgoing; Fri, 27 Sep 1996 12:09:54 -0700 (PDT) Received: from falcon.continet.com (WWW.FINF.COM [206.58.168.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA10755 for ; Fri, 27 Sep 1996 12:09:52 -0700 (PDT) Received: from Default ([206.58.169.79]) by falcon.continet.com (post.office MTA v2.0 0813 ID# 0-10248) with SMTP id AAA89 for ; Fri, 27 Sep 1996 12:20:24 -0700 X-Sender: blackened@continet.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: isp@FreeBsd.Org From: Blackened Date: Fri, 27 Sep 1996 12:20:24 -0700 Message-ID: <19960927192023638.AAA89@Default> Sender: owner-isp@FreeBsd.Org X-Loop: FreeBSD.org Precedence: bulk unsubscribe isp@Freebsd.Org From owner-freebsd-isp Fri Sep 27 12:10:08 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10897 for isp-outgoing; Fri, 27 Sep 1996 12:10:08 -0700 (PDT) Received: from falcon.continet.com (FALCON.CONTINET.COM [206.58.168.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA10874 for ; Fri, 27 Sep 1996 12:10:05 -0700 (PDT) Received: from Default ([206.58.169.79]) by falcon.continet.com (post.office MTA v2.0 0813 ID# 0-10248) with SMTP id AAA196 for ; Fri, 27 Sep 1996 12:20:39 -0700 X-Sender: blackened@continet.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: isp@freebsd.org From: Blackened Date: Fri, 27 Sep 1996 12:20:39 -0700 Message-ID: <19960927192038359.AAA196@Default> Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-isp Fri Sep 27 12:29:48 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA25391 for isp-outgoing; Fri, 27 Sep 1996 12:29:48 -0700 (PDT) Received: from europa.arisia.net (europa.arisia.net [207.100.94.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA25362 for ; Fri, 27 Sep 1996 12:29:45 -0700 (PDT) Received: from mars ([207.100.94.12]) by europa.arisia.net (8.7.5/8.7.3) with SMTP id PAA04090 for ; Fri, 27 Sep 1996 15:33:13 -0400 (EDT) Message-Id: <2.2.32.19960927193337.006ac718@207.100.94.5> X-Sender: msv@207.100.94.5 X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 27 Sep 1996 15:33:37 -0400 To: freebsd-isp@freebsd.org From: "Mark S. Velasquez" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, I know I'm asking a stupid question, but I'll do it anyways : I've installed a 4mm scsi tape drive(a Conner 4326NP) and then dumped my filesystems via the following script : /sbin/dump 0udf 61000 ganymede:/dev/nrst0 / /sbin/dump 0udf 61000 ganymede:/dev/nrst0 /usr /sbin/dump 0udf 61000 ganymede:/dev/nrst0 /var /sbin/dump 0udf 61000 ganymede:/dev/nrst0 /export/home /sbin/dump 0udf 61000 ganymede:/dev/rst0 /export/cache This seems to work fine, however, when I do a "restore -if" to look at the tape, I can only see the first(/) filesystem I dumped. I'm doing an "mt -f /dev/rst0 fsf 1", etc. , to skip to the next dump-file on the tape, but I never get to the next dump. Does mt work on FreeBSD 2.1.5 with my tape drive ? or am I misremembering how to skip to the next dump-file ? Admittedly its been several years since I was involved with system backup. TIA Mark From owner-freebsd-isp Fri Sep 27 15:35:39 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA10221 for isp-outgoing; Fri, 27 Sep 1996 15:35:39 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA10183 for ; Fri, 27 Sep 1996 15:35:31 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id PAA13181; Fri, 27 Sep 1996 15:35:13 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609272235.PAA13181@GndRsh.aac.dev.com> Subject: Re: Restoring from a multidump tape (was: ) In-Reply-To: <2.2.32.19960927193337.006ac718@207.100.94.5> from "Mark S. Velasquez" at "Sep 27, 96 03:33:37 pm" To: msv@arisia.net (Mark S. Velasquez) Date: Fri, 27 Sep 1996 15:35:12 -0700 (PDT) Cc: freebsd-isp@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Well, I know I'm asking a stupid question, but I'll do it anyways : > > I've installed a 4mm scsi tape drive(a Conner 4326NP) and then dumped my > filesystems via the following script : > > /sbin/dump 0udf 61000 ganymede:/dev/nrst0 / > /sbin/dump 0udf 61000 ganymede:/dev/nrst0 /usr > /sbin/dump 0udf 61000 ganymede:/dev/nrst0 /var > /sbin/dump 0udf 61000 ganymede:/dev/nrst0 /export/home > /sbin/dump 0udf 61000 ganymede:/dev/rst0 /export/cache > > This seems to work fine, however, when I do a "restore -if" to look at the > tape, I can only see the first(/) filesystem I dumped. > I'm doing an "mt -f /dev/rst0 fsf 1", etc. , to skip to the next dump-file > on the tape, but I never get to the next dump. Does mt work on FreeBSD 2.1.5 > with my tape drive ? or am I misremembering how to skip to the next > dump-file ? Admittedly its been several years since I was involved with > system backup. Try the following script to produce a TOC of your tape: #!/bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin mt -f /dev/nrst0 rewind restore if /dev/nrst0 mt -f /dev/nrst0 fsf 1 restore if /dev/nrst0 mt -f /dev/nrst0 fsf 1 restore if /dev/nrst0 mt -f /dev/nrst0 fsf 1 restore if /dev/nrst0 mt -f /dev/nrst0 fsf 1 restore if /dev/nrst0 That works just fine for me on my: (ncr0:5:0): "ARCHIVE Python 28388-XXX 4.98" type 1 removable SCSI 2 Aka, Conner 4326RP -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-isp Fri Sep 27 16:12:53 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA29782 for isp-outgoing; Fri, 27 Sep 1996 16:12:53 -0700 (PDT) Received: from mercury.jorsm.com (jeff@[207.112.128.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA29740 for ; Fri, 27 Sep 1996 16:12:45 -0700 (PDT) Received: (from jeff@localhost) by mercury.jorsm.com (8.6.12/8.6.10) id SAA04372; Fri, 27 Sep 1996 18:15:59 -0500 Date: Fri, 27 Sep 1996 18:15:59 -0500 (CDT) From: "Jeff.Lynch-JORSM.Internet" To: "Mark S. Velasquez" cc: freebsd-isp@freebsd.org Subject: Re: your mail In-Reply-To: <2.2.32.19960927193337.006ac718@207.100.94.5> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 27 Sep 1996, Mark S. Velasquez wrote: > I'm doing an "mt -f /dev/rst0 fsf 1", etc. , to skip to the next dump-file try mt -f /dev/nrst0 fsf 1 ========================================================================= 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 Sep 27 19:27:40 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA20897 for isp-outgoing; Fri, 27 Sep 1996 19:27:40 -0700 (PDT) Received: from mailhost.coppe.ufrj.br (root@cisigw.coppe.ufrj.br [146.164.2.31]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA20861 for ; Fri, 27 Sep 1996 19:27:36 -0700 (PDT) Received: (from jonny@localhost) by mailhost.coppe.ufrj.br (8.7.5/8.7.3) id XAA12952; Fri, 27 Sep 1996 23:27:19 -0300 (EST) From: Joao Carlos Mendes Luis Message-Id: <199609280227.XAA12952@mailhost.coppe.ufrj.br> Subject: Re: your mail To: msv@arisia.net (Mark S. Velasquez) Date: Fri, 27 Sep 1996 23:27:19 -0300 (EST) Cc: freebsd-isp@FreeBSD.org In-Reply-To: <2.2.32.19960927193337.006ac718@207.100.94.5> from "Mark S. Velasquez" at "Sep 27, 96 03:33:37 pm" X-Mailer: ELM [version 2.4ME+ PL14 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk #define quoting(Mark S. Velasquez) // Well, I know I'm asking a stupid question, but I'll do it anyways : // // I've installed a 4mm scsi tape drive(a Conner 4326NP) and then dumped my // filesystems via the following script : // // /sbin/dump 0udf 61000 ganymede:/dev/nrst0 / // /sbin/dump 0udf 61000 ganymede:/dev/nrst0 /usr // /sbin/dump 0udf 61000 ganymede:/dev/nrst0 /var // /sbin/dump 0udf 61000 ganymede:/dev/nrst0 /export/home // /sbin/dump 0udf 61000 ganymede:/dev/rst0 /export/cache How did you find 61000 as the tape density ? Is this the right way to force a tape length ? // This seems to work fine, however, when I do a "restore -if" to look at the // tape, I can only see the first(/) filesystem I dumped. // I'm doing an "mt -f /dev/rst0 fsf 1", etc. , to skip to the next dump-file Try: mt -f /dev/nrst0 fsf 1 ^ ^ ^ ^ ^ :) I use this here... // on the tape, but I never get to the next dump. Does mt work on FreeBSD 2.1.5 // with my tape drive ? or am I misremembering how to skip to the next // dump-file ? Admittedly its been several years since I was involved with // system backup. // // TIA // // Mark // // Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro From owner-freebsd-isp Sat Sep 28 00:17:55 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA18878 for isp-outgoing; Sat, 28 Sep 1996 00:17:55 -0700 (PDT) Received: from itchy.mosquito.com (itchy.mosquito.com [206.205.132.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA18849 for ; Sat, 28 Sep 1996 00:17:51 -0700 (PDT) Received: (from boot@localhost) by itchy.mosquito.com (8.7.5/8.6.12) id DAA02418; Sat, 28 Sep 1996 03:21:59 -0400 (EDT) From: Bruce Bauman Message-Id: <199609280721.DAA02418@itchy.mosquito.com> Subject: disk-to-disk copy To: freebsd-isp@freebsd.org Date: Sat, 28 Sep 1996 03:21:59 -0400 (EDT) Cc: boot@itchy.mosquito.com (Bruce Bauman) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have 2 SCSI disks which are going bad, and I've already gotten (identical) replacement drives. I'd like to copy everything (data, partition tables, etc) from the old drives to the new ones. Is there an easy way to do this? Nothing jumped out at me from the man pages. I'd rather not have to go through disklabel, dump, restore, etc. Thanks. -- Bruce From owner-freebsd-isp Sat Sep 28 00:52:20 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA16147 for isp-outgoing; Sat, 28 Sep 1996 00:52:20 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA16106 for ; Sat, 28 Sep 1996 00:52:17 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id AAA14955; Sat, 28 Sep 1996 00:52:00 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609280752.AAA14955@GndRsh.aac.dev.com> Subject: Re: disk-to-disk copy In-Reply-To: <199609280721.DAA02418@itchy.mosquito.com> from Bruce Bauman at "Sep 28, 96 03:21:59 am" To: boot@mosquito.com (Bruce Bauman) Date: Sat, 28 Sep 1996 00:51:55 -0700 (PDT) Cc: freebsd-isp@freebsd.org, boot@itchy.mosquito.com X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have 2 SCSI disks which are going bad, and I've already > gotten (identical) replacement drives. I'd like to copy > everything (data, partition tables, etc) from the old drives > to the new ones. Is there an easy way to do this? > > Nothing jumped out at me from the man pages. I'd rather > not have to go through disklabel, dump, restore, etc. If they are truely identical in block count this will do it: dd if=/dev/rsdX of=/dev/rsdY bs=8192 Note that hard errors are going to cause this to abort, so turn on ARRE to try and minimize them with: scsi -f /dev/rsdX -m 1 -P3 -e -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-isp Sat Sep 28 11:51:45 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14518 for isp-outgoing; Sat, 28 Sep 1996 11:51:45 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA14478 for ; Sat, 28 Sep 1996 11:51:42 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id LAA26845; Sat, 28 Sep 1996 11:51:33 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id LAA00393; Sat, 28 Sep 1996 11:51:27 -0700 (PDT) Message-Id: <199609281851.LAA00393@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Bruce Bauman cc: freebsd-isp@freebsd.org, boot@itchy.mosquito.com (Bruce Bauman) Subject: Re: disk-to-disk copy In-reply-to: Your message of Sat, 28 Sep 96 03:21:59 -0400. <199609280721.DAA02418@itchy.mosquito.com> Date: Sat, 28 Sep 1996 11:51:21 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [...] >gotten (identical) replacement drives. I'd like to copy >everything (data, partition tables, etc) from the old drives >to the new ones. Is there an easy way to do this? >Nothing jumped out at me from the man pages. I'd rather >not have to go through disklabel, dump, restore, etc. If the drives are *exactly* the same, you can use dd from one raw device to the other (dd -if=/dev/rsd0c -of=/dev/rsd1c) (those are from memory, so excuse if I messed up the syntax slightly). If they aren't identical, you will need to put a disklabel on the new drive, newfs its filesystems, then copy the files. The most common way to copy all the data intact is: cd /olddir ; tar -cplf . | ( cd /newdir ; tar -xp --unlink --file - ) This will not traverse a mount point (which is what you want), so you'll have to do / and /usr separately (and any other things you have mounted that you want to copy. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-isp Sat Sep 28 12:26:51 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA13387 for isp-outgoing; Sat, 28 Sep 1996 12:26:51 -0700 (PDT) Received: from shadows.aeon.net (bsdscsi@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA12982; Sat, 28 Sep 1996 12:26:20 -0700 (PDT) Received: (from bsdscsi@localhost) by shadows.aeon.net (8.7.5/8.6.9) id WAA05358; Sat, 28 Sep 1996 22:25:45 +0300 (EET DST) From: mika ruohotie Message-Id: <199609281925.WAA05358@shadows.aeon.net> Subject: Re: striping/mirroring? To: freebsd-isp@freebsd.org Date: Sat, 28 Sep 1996 22:25:45 +0300 (EET DST) Cc: scsi@freebsd.org In-Reply-To: from Richard Wackerbarth at "Sep 28, 96 06:15:34 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm lost. How can the mirror be slower than the drive that it is mirroring > unless it is a "read mostly" situation and you are guaranteed no write > bursts? hmm? > >seems to me answer is no. > I think that the answer is "yes". You can you elaborate? Describe the > configuration that you have in mind. ack... i admit first i had minor thinking error when i was planning the system at the first time... now, what i want to do is this: strip with few drives, so that i can get speed, and then mirror it all to one "safe" disk, so that i wont lost all of my data if the striping crashes... but now that i think of it, i will lose all the speed i would gain by using ccd if i'd have to "wait" until it's all being written to a one drive... so i would love to hear suggestions how to get more speed than just mounting my system thru several drives, but still having some "safety" left... actually, so that i wont waste any more of anyone's time, i think i can settle down if i get an opinion/numbers how much slower the disks will perform if i use four 2gig drives (two channel adapter used) compared if i would use them ccded? the server will be www/ftp machine which should be as fast as possible, still being safe what comes to loss of data in crashes... i was planning to run 2.1.5 on it. or should i use -current? (sent to freebsd-isp too since i think this is more isp related) mickey -- mika@aeon.net mika ruohotie net/sys admin From owner-freebsd-isp Sat Sep 28 14:15:38 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18787 for isp-outgoing; Sat, 28 Sep 1996 14:15:38 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18678; Sat, 28 Sep 1996 14:15:26 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id QAA00554; Sat, 28 Sep 1996 16:13:37 -0500 From: Joe Greco Message-Id: <199609282113.QAA00554@brasil.moneng.mei.com> Subject: Re: striping/mirroring? To: bsdscsi@shadows.aeon.net (mika ruohotie) Date: Sat, 28 Sep 1996 16:13:37 -0500 (CDT) Cc: freebsd-isp@freebsd.org, scsi@freebsd.org In-Reply-To: <199609281925.WAA05358@shadows.aeon.net> from "mika ruohotie" at Sep 28, 96 10:25:45 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > strip with few drives, so that i can get speed, and then mirror it all > to one "safe" disk, so that i wont lost all of my data if the striping > crashes... Having used ccd extensively for the past year, on production news server systems, I think I can safely state that you need not concern yourself too much with "striping crashes"... you are more likely to run into a dead disk than a problem with ccd. I have over two dozen heavily utilized ccd partitions in operation and have not seen any problems with ccd. If you are looking purely for reliability, look for a RAID solution. RAID's are more reliable than a SLED (Single Large Expensive Disk). If you are looking for speed, either RAID or striping may be appropriate. Since I am generally interested primarily in speed, I use ccd and its striping capabilities. ... JG