From owner-freebsd-isp Sun Oct 18 07:42:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20611 for freebsd-isp-outgoing; Sun, 18 Oct 1998 07:42:45 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from magicnet.magicnet.net (magicnet.magicnet.net [204.96.116.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20596 for ; Sun, 18 Oct 1998 07:42:42 -0700 (PDT) (envelope-from bill@bilver.magicnet.net) Received: (from uucp@localhost) by magicnet.magicnet.net (8.8.6/8.8.8) with UUCP id KAA01369 for freebsd-isp@freebsd.org; Sun, 18 Oct 1998 10:38:50 -0400 (EDT) Received: (from bill@localhost) by bilver.magicnet.net (8.9.1/8.9.1) id KAA06597 for freebsd-isp@freebsd.org; Sun, 18 Oct 1998 10:37:16 -0400 (EDT) From: Bill Vermillion Message-Id: <199810181437.KAA06597@bilver.magicnet.net> Subject: Re: Don't bet on 3.0 release To: freebsd-isp@FreeBSD.ORG Date: Sun, 18 Oct 1998 10:37:16 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg Lehey recently said: > On Sunday, 18 October 1998 at 0:18:51 +0100, Karl Pielorz wrote: > > Paul Stewart wrote: > >> We just upgraded our main commerical web server to 3.0-RELEASE > >> and everything works like a dream except I can't compile > >> apache-ssl for our secure server... as it's compiling, I get > >> the following from the SSLeahy port... > > Not wanting to start fireworks, but if it's your _main_ > > commercial / production box you probably shouln't have done > > that... If you look through the -current mailing list you would > > have seen why... A lot of the ports, and other software have > > problems with ELF at the moment... > To be fair, 3.0 has now been released, and you can't expect that > everybody who's now thinking of installing to have been reading > -current all this time. Well there was plenty of notice/warning about 3.0 being the first cut and was to be for experimentors and early adopters. I got a notice on my subscription about 2 months ago - and they suggested that you wait until at least 3.1 for a production environment. Installing a new release on a production system within days of its' release always has the chance of being dicey. No matter how much you beta test something still seems to come out that was missed. On another OS I just got a 56 page list of bugs that were fixed from the previous version to the shipping version. There were some very good people on the beta test for months - and there are still things popping up that weren't seen before. Bugs beget bugs. Or removing one makes another bug apparent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Oct 18 08:50:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02118 for freebsd-isp-outgoing; Sun, 18 Oct 1998 08:50:13 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02112 for ; Sun, 18 Oct 1998 08:50:11 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbws.vastnet.net (port25.netsvr1.cst.vastnet.net [207.252.73.25]) by etinc.com (8.8.8/8.6.9) with SMTP id LAA13775; Sun, 18 Oct 1998 11:47:49 GMT Message-Id: <3.0.32.19981018114951.00723bc8@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 18 Oct 1998 11:49:54 -0400 To: Bill Vermillion , freebsd-isp@FreeBSD.ORG From: Dennis Subject: Re: Don't bet on 3.0 release Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 10:37 AM 10/18/98 -0400, Bill Vermillion wrote: >Greg Lehey recently said: >> On Sunday, 18 October 1998 at 0:18:51 +0100, Karl Pielorz wrote: > >> > Paul Stewart wrote: > >> >> We just upgraded our main commerical web server to 3.0-RELEASE >> >> and everything works like a dream except I can't compile >> >> apache-ssl for our secure server... as it's compiling, I get >> >> the following from the SSLeahy port... > >> > Not wanting to start fireworks, but if it's your _main_ >> > commercial / production box you probably shouln't have done >> > that... If you look through the -current mailing list you would >> > have seen why... A lot of the ports, and other software have >> > problems with ELF at the moment... > >> To be fair, 3.0 has now been released, and you can't expect that >> everybody who's now thinking of installing to have been reading >> -current all this time. > >Well there was plenty of notice/warning about 3.0 being the first >cut and was to be for experimentors and early adopters. I got a >notice on my subscription about 2 months ago - and they suggested >that you wait until at least 3.1 for a production environment. > >Installing a new release on a production system within days of its' >release always has the chance of being dicey. No matter how much >you beta test something still seems to come out that was missed. -RELEASE implies that its ready for the general public. If its still in BETA, which your comments indicate it is, then it should not be released. What's the point of doing a release if its not ready? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Oct 18 09:15:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05797 for freebsd-isp-outgoing; Sun, 18 Oct 1998 09:15:26 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from bugsy.indra.de (bugsy.indra.de [193.158.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05780 for ; Sun, 18 Oct 1998 09:15:17 -0700 (PDT) (envelope-from deuerl@bugsy.indra.de) Received: (from deuerl@localhost) by bugsy.indra.de (8.8.8/8.8.8) id QAA10574 for freebsd-isp@freebsd.org; Sun, 18 Oct 1998 16:28:52 GMT (envelope-from deuerl) From: Robert Deuerling Message-Id: <199810181628.QAA10574@bugsy.indra.de> Subject: clustering under freebsd ? To: freebsd-isp@FreeBSD.ORG Date: Sun, 18 Oct 1998 16:28:52 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, since FreeBSD is the most stable software :-) there's only the hardware, which can put the server down.... Is there a solution for having a backup server in the net, which comes up, when the primary server goes down... Or how can i solve this prob... Any ideas are very welcome ;) -Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Oct 18 09:54:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12581 for freebsd-isp-outgoing; Sun, 18 Oct 1998 09:54:58 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12552 for ; Sun, 18 Oct 1998 09:54:48 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id MAA14101; Sun, 18 Oct 1998 12:51:36 -0400 (EDT) Date: Sun, 18 Oct 1998 12:51:36 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Dennis cc: Bill Vermillion , freebsd-isp@FreeBSD.ORG Subject: Re: Don't bet on 3.0 release In-Reply-To: <3.0.32.19981018114951.00723bc8@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 18 Oct 1998, Dennis wrote: > -RELEASE implies that its ready for the general public. If its still in > BETA, which your comments indicate it is, then it should not > be released. What's the point of doing a release if its not ready? What I got from the announcement is that it's targetted to the following people: workstation users, tinkerers, folks who are using some snap of 3.0 in production already for a new feature, and those that can work their way around problems that didn't come up in the beta test stage. As for why it's released? I'd guess you can't be in beta forever. There's always 2.2.8 if you are attached to that branch for it's stability. Charles > > Dennis > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Oct 18 10:00:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13456 for freebsd-isp-outgoing; Sun, 18 Oct 1998 10:00:54 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13450 for ; Sun, 18 Oct 1998 10:00:51 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id RAA00857; Sun, 18 Oct 1998 17:59:29 +0100 (BST) Date: Sun, 18 Oct 1998 17:59:29 +0100 (BST) From: Karl Pielorz To: Dennis cc: Bill Vermillion , freebsd-isp@FreeBSD.ORG Subject: Re: Don't bet on 3.0 release In-Reply-To: <3.0.32.19981018114951.00723bc8@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 18 Oct 1998, Dennis wrote: > -RELEASE implies that its ready for the general public. If its still in > BETA, which your comments indicate it is, then it should not > be released. What's the point of doing a release if its not ready? 3.0-RELEASE is not in beta, it is a relase. The idea is that a lot more people can have a look at it, review it - try it - and see how far FreeBSD has come... It's not suitable for everyone (and carries warnings to that effect), and shouldn't be installed on an 'ad-hoc' basis on production boxes (unless you _really_ know what your doing - and are prepared to work closely with it - if needs be). Here we run several 2.2.X boxes for our ISP service... I have few qualms about moving them through the 2.2.X tree (i.e. I install 2.2.5, I don't mind upgrading it to 2.2.7 - nor 2.2.8 when it comes out) - I wouldn't just slap 3.0-RELEASE on it after having read the release notes... Will you be rushing to install Windows NT 5 on all your production servers the day it's released next year? - Probably not... Anyway, I don't want to get into or start any flame wars over this - the above is my oppinion, it's the way I normally handle new releases of FreeBSD - it works for me - it's not going to be the way everyone else does, or want's to do it... I'm quite happy with 3.0-RELEASE being around, I've already got 2 Linux convertee's already ;-) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Oct 18 10:38:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16984 for freebsd-isp-outgoing; Sun, 18 Oct 1998 10:38:33 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16979 for ; Sun, 18 Oct 1998 10:38:30 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id MAA13790; Sun, 18 Oct 1998 12:36:36 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <362A2724.163B757F@webwizard.org.mx> Date: Sun, 18 Oct 1998 12:36:36 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: spork CC: Dennis , Bill Vermillion , freebsd-isp@FreeBSD.ORG Subject: Re: Don't bet on 3.0 release References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org spork wrote: > On Sun, 18 Oct 1998, Dennis wrote: > > > -RELEASE implies that its ready for the general public. If its still in > > BETA, which your comments indicate it is, then it should not > > be released. What's the point of doing a release if its not ready? > > What I got from the announcement is that it's targetted to the following > people: workstation users, tinkerers, folks who are using some snap of > 3.0 in production already for a new feature, and those that can work their > way around problems that didn't come up in the beta test stage. As for > why it's released? I'd guess you can't be in beta forever. There's > always 2.2.8 if you are attached to that branch for it's stability. > > Charles IMHO, I think it's time to break a paradigm:-) There no real releases any more nor is there a need for them, there are "real-time snapshots" that can be downloaded whenever a person wants. Some are better and some are worse, but we don't have to and I think shouldn't follow the commercial software lead of releases (Especially, Micro$oft:-). This paradigm was valid before the Internet but is now obsolete. As an example, we've been using 3.0 for production servers scattered all over Mexico and performing remote updates and maintenance from our offices. with NO operating system related problems for almost a year now. The server uptime is only limited by our making world, making a kernel and rebooting from 2 to 4 times a month. Would our using a release make this better? If we think back, things run smoothly until someone says, "Tomorrow we freeze code for a release" and all hell breaks loose:-) When the smoke clears, most of us will continue cvsuping and making world daily, irregardless of release or beta or alfa.:-) It's just too damn easy and stimulating not to:-) ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Oct 18 11:02:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19213 for freebsd-isp-outgoing; Sun, 18 Oct 1998 11:02:46 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from magicnet.magicnet.net (magicnet.magicnet.net [204.96.116.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19208 for ; Sun, 18 Oct 1998 11:02:45 -0700 (PDT) (envelope-from bill@bilver.magicnet.net) Received: (from uucp@localhost) by magicnet.magicnet.net (8.8.6/8.8.8) with UUCP id NAA01182 for freebsd-isp@freebsd.org; Sun, 18 Oct 1998 13:59:18 -0400 (EDT) Received: (from bill@localhost) by bilver.magicnet.net (8.9.1/8.9.1) id NAA08216 for freebsd-isp@freebsd.org; Sun, 18 Oct 1998 13:53:30 -0400 (EDT) From: Bill Vermillion Message-Id: <199810181753.NAA08216@bilver.magicnet.net> Subject: Re: Don't bet on 3.0 release In-Reply-To: <3.0.32.19981018114951.00723bc8@etinc.com> from Dennis at "Oct 18, 98 11:49:54 am" To: freebsd-isp@FreeBSD.ORG Date: Sun, 18 Oct 1998 13:53:30 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dennis recently said: > At 10:37 AM 10/18/98 -0400, Bill Vermillion wrote: > >Greg Lehey recently said: > >Well there was plenty of notice/warning about 3.0 being the first > >cut and was to be for experimentors and early adopters. I got a > >notice on my subscription about 2 months ago - and they suggested > >that you wait until at least 3.1 for a production environment. > >Installing a new release on a production system within days of its' > >release always has the chance of being dicey. No matter how much > >you beta test something still seems to come out that was missed. > -RELEASE implies that its ready for the general public. If its > still in BETA, which your comments indicate it is, then it should > not be released. What's the point of doing a release if its not > ready? Well I have been doing beta testing on a Unix release (not FreeBSD) for a couple of months. Guess what - when it went into general production - and the final CDs were pressed - not the Kodak writable CDs we were getting as beta tester- a few more bugs popped up. You can test everything for all pieces of hardware - because someone will always find a combination that is not tested, or a keystroke combination that was not tested for, etc. About the only programming that normally seems to be bulletproof - at least in more cases than not - are the OSes and control programs in ROMs for embedded controls. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Oct 19 02:30:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12367 for freebsd-isp-outgoing; Mon, 19 Oct 1998 02:30:21 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from velvet.sensation.net.au (serial0-velvet.Brunswick.sensation.net.au [203.20.114.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12360 for ; Mon, 19 Oct 1998 02:30:16 -0700 (PDT) (envelope-from rowan@sensation.net.au) Received: from localhost (rowan@localhost) by velvet.sensation.net.au (8.8.8/8.8.8) with SMTP id TAA28201 for ; Mon, 19 Oct 1998 19:26:42 +1000 (EST) (envelope-from rowan@sensation.net.au) X-Authentication-Warning: velvet.sensation.net.au: rowan owned process doing -bs Date: Mon, 19 Oct 1998 19:26:38 +1000 (EST) From: Rowan Crowe To: freebsd-isp@FreeBSD.ORG Subject: Re: Multilink PPP daemon for FreeBSD - not mpd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, Since I can't seem to find any other options for multilink PPP under FreeBSD I think I'll have to [lower lip trembles] go with mpd. ;-) I've looked at it a couple of times before and because it's based on user level ppp it's a little alien to me, but even more so because the sample config files are for a *client* setup (ie a dialout). Is anyone running mpd as a *server*? If so I'd appreciate it if I could have a peek at your config files... TIA. Cheers. -- Rowan Crowe Sensation Internet Services, Melbourne Aust fidonet: 3:635/728 +61-3-9388-9260 http://www.rowan.sensation.net.au/ http://www.sensation.net.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 04:14:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04347 for freebsd-isp-outgoing; Tue, 20 Oct 1998 04:14:40 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04342 for ; Tue, 20 Oct 1998 04:14:37 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.8.8/8.8.8) id EAA01465; Tue, 20 Oct 1998 04:14:10 -0700 (PDT) Message-ID: <19981020041410.35287@cpl.net> Date: Tue, 20 Oct 1998 04:14:10 -0700 From: Shawn Ramsey To: "et-users@etinc.com" Cc: isp@FreeBSD.ORG Subject: startup problem References: <01BDFB91.7A1A1000.William.Stucke@zanet.co.za> <199810191344.NAA18823@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199810191344.NAA18823@etinc.com>; from Dennis on Mon, Oct 19, 1998 at 01:57:35PM -0400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We are having trouble with one of our FreeBSD-2.2.7-Stable servers. We are loading all the ET utils out of rc.local. I relize this may not be the best place to do it.. but it had worked fine up to now. The problem is, since upgrading the driver to 3.0g, and updating the utils from 2.x.. it seems to load them on bootup, as it dumps it to the screen. But nothing seems to happen. The routing table is the same as before they hadn't loaded. After the system is up, and I run rc.local by hand, everything is fine. If we revery back to 2.x, everything is fine. Any ideas? Is there a better way to configure ports other than having everything in rc.local? Moving a small part of rc.local to /usr/local/etc/rc.d, same effect. Thanks for any suggestions... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 05:25:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10163 for freebsd-isp-outgoing; Tue, 20 Oct 1998 05:25:13 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from unix.kawartha.com (unix.kawartha.com [204.101.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10156 for ; Tue, 20 Oct 1998 05:25:10 -0700 (PDT) (envelope-from pstewart@kawartha.com) Received: from shell.kawartha.com (shell.kawartha.com [204.101.15.43]) by unix.kawartha.com (8.8.8/8.8.7) with SMTP id IAA18268 for ; Tue, 20 Oct 1998 08:29:20 -0400 (EDT) Date: Tue, 20 Oct 1998 08:46:35 -0400 (EDT) From: Paul Stewart To: freebsd-isp@FreeBSD.ORG Subject: 3.0 Upgrade Question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org HI there.... I would first like to thank everyone for their response to my secure server not working in 3.0-RELEASE.... I shouldn't have played with fire..:) Since, I have re-installed the server to 2.2.7-RELEASE and everything is working fine.... thank you. On a side note, we have several machines running on 122597-SNAP releases. They are running just fine except I can't compile UCD-SNMP on them which is now needed. So, I was thinking of updating them to 3.0-RELEASE. Am I playing with fire again? I can't take these machines offline for a long period of time. Can I CVSUP them to the newest kernel trees and remake the kernel? Is this a safe practice? As you can tell, I'm not used to upgrading these machines. They run currently like a dream but I don't want to fall a LONG ways behind in the current kernels...:) Thanks for your input... Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 06:51:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18163 for freebsd-isp-outgoing; Tue, 20 Oct 1998 06:51:22 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18158 for ; Tue, 20 Oct 1998 06:51:19 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id OAA00478; Tue, 20 Oct 1998 14:50:45 +0100 (BST) Message-ID: <362C94ED.2A49B872@tdx.co.uk> Date: Tue, 20 Oct 1998 14:49:33 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Paul Stewart CC: freebsd-isp@FreeBSD.ORG Subject: Re: 3.0 Upgrade Question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Paul Stewart wrote: > On a side note, we have several machines running on 122597-SNAP releases. > They are running just fine except I can't compile UCD-SNMP on them which > is now needed. So, I was thinking of updating them to 3.0-RELEASE. Am I > playing with fire again? I can't take these machines offline for a long > period of time. Can I CVSUP them to the newest kernel trees and remake > the kernel? Is this a safe practice? If you mean run a 3.0 kernel with a 2.2.7 utils/bin tree? - No, that's asking for trouble... It would brake lots of things like ps etc. just for starters... (If that is what you meant?) > As you can tell, I'm not used to upgrading these machines. They run > currently like a dream but I don't want to fall a LONG ways behind in the > current kernels...:) Until a couple of months ago, our main production boxes were all running 2.2.2... We've upgraded them to 2.2.7 (mainly to get better pppd support) - they won't be going anywhere fast for a while either... When we took them down they both had uptimes well into the 350+ days :) - I guess with stuff this reliable it's easy for boxes to get out of date until you either find a problem - or want something they can't do (in 2.2.2, but can in 2.2.7 etc. ;-) If you really need UCD-SNMP (which I'll confess I don't really know what it is - some sort of snmp daemon/service?) - maybe someone can come up with a way of compiling it on 2.2.7 - unless it's really kernel dependant :( Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 07:49:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22223 for freebsd-isp-outgoing; Tue, 20 Oct 1998 07:49:50 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from unix.kawartha.com (unix.kawartha.com [204.101.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22212 for ; Tue, 20 Oct 1998 07:49:46 -0700 (PDT) (envelope-from pstewart@kawartha.com) Received: from shell.kawartha.com (shell.kawartha.com [204.101.15.43]) by unix.kawartha.com (8.8.8/8.8.7) with SMTP id KAA24388; Tue, 20 Oct 1998 10:53:40 -0400 (EDT) Date: Tue, 20 Oct 1998 11:10:56 -0400 (EDT) From: Paul Stewart To: Karl Pielorz cc: freebsd-isp@FreeBSD.ORG Subject: Re: 3.0 Upgrade Question In-Reply-To: <362C94ED.2A49B872@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What about running the upgrade feature in sysinstall?? This would upgrade the entire box correct? OR, is it wise to install whatever version we want onto a new server and then transfer over the user files etc. one by one...:) Paul On Tue, 20 Oct 1998, Karl Pielorz wrote: > > Paul Stewart wrote: > > > On a side note, we have several machines running on 122597-SNAP releases. > > They are running just fine except I can't compile UCD-SNMP on them which > > is now needed. So, I was thinking of updating them to 3.0-RELEASE. Am I > > playing with fire again? I can't take these machines offline for a long > > period of time. Can I CVSUP them to the newest kernel trees and remake > > the kernel? Is this a safe practice? > > If you mean run a 3.0 kernel with a 2.2.7 utils/bin tree? - No, that's asking > for trouble... It would brake lots of things like ps etc. just for starters... > (If that is what you meant?) > > > As you can tell, I'm not used to upgrading these machines. They run > > currently like a dream but I don't want to fall a LONG ways behind in the > > current kernels...:) > > Until a couple of months ago, our main production boxes were all running > 2.2.2... We've upgraded them to 2.2.7 (mainly to get better pppd support) - > they won't be going anywhere fast for a while either... When we took them down > they both had uptimes well into the 350+ days :) - I guess with stuff this > reliable it's easy for boxes to get out of date until you either find a > problem - or want something they can't do (in 2.2.2, but can in 2.2.7 etc. ;-) > > If you really need UCD-SNMP (which I'll confess I don't really know what it is > - some sort of snmp daemon/service?) - maybe someone can come up with a way of > compiling it on 2.2.7 - unless it's really kernel dependant :( > > Regards, > > Karl > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 08:06:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23746 for freebsd-isp-outgoing; Tue, 20 Oct 1998 08:06:12 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gateway.blueberry.co.uk (gateway.blueberry.co.uk [195.153.48.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23741 for ; Tue, 20 Oct 1998 08:06:11 -0700 (PDT) (envelope-from keith@blueberry.co.uk) Received: from intranet.blueberry.co.uk (intranet.internal.blueberry.co.uk [10.0.0.2]) by gateway.blueberry.co.uk (8.8.8/8.8.8) with ESMTP id QAA09435 for ; Tue, 20 Oct 1998 16:05:36 +0100 (BST) (envelope-from keith@blueberry.co.uk) Received: (from keith@localhost) by intranet.blueberry.co.uk (8.8.8/8.8.8) id QAA21113; Tue, 20 Oct 1998 16:05:36 +0100 (BST) (envelope-from keith) Message-ID: <19981020160536.49920@blueberry.co.uk> Date: Tue, 20 Oct 1998 16:05:36 +0100 From: Keith Jones To: freebsd-isp@FreeBSD.ORG Subject: Re: 3.0 Upgrade Question References: <362C94ED.2A49B872@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <362C94ED.2A49B872@tdx.co.uk>; from Karl Pielorz on Tue, Oct 20, 1998 at 02:49:33PM +0100 Organization: Blueberry New Media Ltd. Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 20, 1998 at 02:49:33PM +0100, Karl Pielorz wrote: > If you really need UCD-SNMP (which I'll confess I don't really know what it is > - some sort of snmp daemon/service?) - maybe someone can come up with a way of > compiling it on 2.2.7 - unless it's really kernel dependant :( UCD-SNMP works fine under 2.2.7 AFAICT - or at least under -STABLE. We've been running it on our FreeBSD servers since the beginning of July with no problems. On the point of choosing between 2.2.7-R (or -S) and 3.0-R, it might be better to stick with the former as 3.0-R is (as with any x.0 release) likely to be a little less stable than 2.2.7. The cue to switch to 3.0[.x?] is probably when 3.0-STABLE starts to appear. Keith -- v Keith Jones Systems Manager, Blueberry Group Ltd. v | Postal Mail: 2/10 Harbour Yard, Chelsea Harbour, LONDON, UK. SW10 0XD | | Telephone: +44 (0)171 351 3313 Fax: +44 (0)171 351 2476 | ^ Email: Keith.Jones@blueberry.co.uk WWW: http://www.blueberry.co.uk/ ^ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 08:12:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24361 for freebsd-isp-outgoing; Tue, 20 Oct 1998 08:12:07 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail.intercom.com ([207.51.55.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24354 for ; Tue, 20 Oct 1998 08:12:06 -0700 (PDT) (envelope-from jason@intercom.com) Received: from localhost (jason@localhost) by mail.intercom.com (8.9.0/8.9.0) with SMTP id LAA16928 for ; Tue, 20 Oct 1998 11:11:44 -0400 (EDT) Date: Tue, 20 Oct 1998 11:11:43 -0400 (EDT) From: jason To: freebsd-isp@FreeBSD.ORG Subject: Batch installs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have searched on the freebsd site for a way to do batch installs, but have come up with nothing. Is there a way to have a file that states all the things you would like to install, etc to make installing on several servers easier? - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 08:20:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25254 for freebsd-isp-outgoing; Tue, 20 Oct 1998 08:20:44 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25249 for ; Tue, 20 Oct 1998 08:20:42 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id QAA00792; Tue, 20 Oct 1998 16:20:12 +0100 (BST) Message-ID: <362CA9E4.57ABD3C0@tdx.co.uk> Date: Tue, 20 Oct 1998 16:19:00 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Paul Stewart CC: freebsd-isp@FreeBSD.ORG Subject: Re: 3.0 Upgrade Question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Paul Stewart wrote: > > What about running the upgrade feature in sysinstall?? This would upgrade > the entire box correct? > > OR, is it wise to install whatever version we want onto a new server and > then transfer over the user files etc. one by one...:) > > Paul Hmmm... I'm not sure Sysinstall's upgrade will handle 2.2.7 to 3.0... I've never used it though, I seem to remember getting as far as the 'impending doom' screens... When we install our boxes here we do them from clean, we have install logs for them that list the distributions that were put on, the ports that were added - and how the applications (e.g. apache etc.) were setup, so we're quite lucky... You might want to check in -current and the archives to see what issues surround going from 2.2.7 to 3.0... A seperate box might be the 'ideal' way to go if you have the spare boxes, and always remember to back the system up Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 08:42:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27312 for freebsd-isp-outgoing; Tue, 20 Oct 1998 08:42:11 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from smtp.shellnet.co.uk (smtp.shellnet.co.uk [194.129.209.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27304 for ; Tue, 20 Oct 1998 08:42:08 -0700 (PDT) (envelope-from steven@shellnet.co.uk) Received: from STEVENF (eth2-fw1.bolton.shellnet.co.uk [194.129.209.8]) by smtp.shellnet.co.uk (8.9.1/8.9.1-shellnet.stevenf) with SMTP id QAA25819 for ; Tue, 20 Oct 1998 16:42:05 +0100 (BST) Posted-Date: Tue, 20 Oct 1998 16:42:05 +0100 (BST) From: steven@shellnet.co.uk (Steven Fletcher) To: freebsd-isp@FreeBSD.ORG Subject: INN control/junk files Date: Tue, 20 Oct 1998 15:41:56 GMT Message-ID: <362c9e0e.261287321@smtp.shellnet.co.uk> X-Mailer: Forte Agent 1.5/32.452 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA27306 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just been twiddling my thumbs with INN, however as soon as I attempt to run innd, the following apprears (I setup syslogd to log !inn *.* to root): Oct 20 15:35:58 nntp innd: Reading config from /usr/local/news/etc/inn.conf Oct 20 15:35:58 nntp innd: SERVER descriptors 360 Oct 20 15:35:58 nntp innd: SERVER outgoing 347 Oct 20 15:35:58 nntp innd: SERVER ccsetup control:11 Oct 20 15:35:58 nntp innd: SERVER lcsetup localconn:13 Oct 20 15:35:58 nntp innd: SERVER rcsetup remconn:4 Oct 20 15:35:58 nntp innd: SERVER internal no control and/or junk group What am I missing? Thanks for any advice here. Steven Fletcher steven@shellnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 09:15:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02114 for freebsd-isp-outgoing; Tue, 20 Oct 1998 09:15:48 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA02109 for ; Tue, 20 Oct 1998 09:15:46 -0700 (PDT) (envelope-from reich@internetcds.com) Received: (qmail 28954 invoked from network); 20 Oct 1998 16:15:19 -0000 Received: from godiva.office.cdsnet.net (HELO godiva) (204.118.245.11) by mail.cdsnet.net with SMTP; 20 Oct 1998 16:15:19 -0000 Message-Id: <4.1.0.67.19981020091618.00a66ac0@martini.office.cdsnet.net> X-Sender: reich@mail.cdsnet.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.67 (Beta) Date: Tue, 20 Oct 1998 09:17:18 -0700 To: freebsd-isp@FreeBSD.ORG From: Mahlon Smith Subject: Re: INN control/junk files In-Reply-To: <362c9e0e.261287321@smtp.shellnet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To: steven@shellnet.co.uk (Steven Fletcher) Subject: Re: INN control/junk files Cc: At 03:41 PM 10/20/98 +0000, you wrote: >I've just been twiddling my thumbs with INN, however as soon as I >attempt to run innd, the following apprears (I setup syslogd to log >!inn *.* to root): > >Oct 20 15:35:58 nntp innd: SERVER internal no control and/or junk >group > >What am I missing? Thanks for any advice here. > > >Steven Fletcher >steven@shellnet.com --------------------------------------------------------------- Your active file needs to contain groups called control and junk - The easiest way to do it is to ~news/bin/ctlinnd newgroup control ~news/bin/ctlinnd newgroup junk I also like to add a line in the ~news/etc/nnrp.access file, something like [allowed-hosts]:Read Post:::*,!junk,!control So the control and junk groups aren't displayed to the readers. Be sure and run ~news/bin/inncheck to see if you've got any other problems before you fire up rc.news. Mahlon ------------ Mahlon Smith InternetCDS 541.773.9600 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 10:48:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12288 for freebsd-isp-outgoing; Tue, 20 Oct 1998 10:48:57 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from guardian.fortress.org (guardian-ext.fortress.org [199.202.137.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12273 for ; Tue, 20 Oct 1998 10:48:50 -0700 (PDT) (envelope-from andrew@guardian.fortress.org) Received: from localhost (andrew@localhost) by guardian.fortress.org (8.8.8/8.8.8) with SMTP id NAA09059; Tue, 20 Oct 1998 13:48:23 -0400 (EDT) (envelope-from andrew@guardian.fortress.org) Date: Tue, 20 Oct 1998 13:48:23 -0400 (EDT) From: Andrew Webster Reply-To: andrew@pubnix.net To: freebsd-isp@FreeBSD.ORG Subject: INN/CCD Question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am happy to report that ccd/inn is a great combination and has been running with excellent results since I implemented this. However, I have two small memory related problems when the system intially boots. The system is running on a P233 with 128MB ram and a 18GB ccd array for the spool on 2.2.5-Stable. During the boot, the fsck -p can't fsck the ccd because of a memory allocation problem. I've made sure that the swapon -a and the ccdconfig take place BEFORE the fsck. If I run fsck by hand in the shell, it works fine though. I have a similar problem when inn starts (rc.news run from rc.local), it cannot malloc enough memory, but if I run rc.news by hand from a root shell, it works just fine. Are these 2 problems related, and what do I need to tune to fix them? Thanks in advance! Andrew Webster andrew@pubnix.net Key fingerprint = CF E8 16 B8 A6 DB E3 C9 83 E7 96 24 25 58 15 6E PubNIX Montreal Connected to the world Branche au monde P.O. Box 147 Cote Saint Luc, Quebec H4V 2Y3 tel 514.990.5911 http://www.pubnix.net fax 514.990.9443 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 11:40:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17758 for freebsd-isp-outgoing; Tue, 20 Oct 1998 11:40:31 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17752 for ; Tue, 20 Oct 1998 11:40:28 -0700 (PDT) (envelope-from druber@mail.kersur.net) Received: from localhost (druber@localhost) by mail.kersur.net (8.8.8/8.8.8) with SMTP id OAA17484; Tue, 20 Oct 1998 14:40:45 -0400 (EDT) Date: Tue, 20 Oct 1998 14:40:45 -0400 (EDT) From: Dan Swartzendruber To: andrew@pubnix.net cc: freebsd-isp@FreeBSD.ORG Subject: Re: INN/CCD Question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 20 Oct 1998, Andrew Webster wrote: > > I am happy to report that ccd/inn is a great combination and has been > running with excellent results since I implemented this. > > However, I have two small memory related problems when the system intially > boots. > > The system is running on a P233 with 128MB ram and a 18GB ccd array for > the spool on 2.2.5-Stable. > > During the boot, the fsck -p can't fsck the ccd because of a memory > allocation problem. I've made sure that the swapon -a and the ccdconfig > take place BEFORE the fsck. If I run fsck by hand in the shell, it works > fine though. > > I have a similar problem when inn starts (rc.news run from rc.local), it > cannot malloc enough memory, but if I run rc.news by hand from a root > shell, it works just fine. /etc/login.conf. The daemon class is relevant when booting, but when you do it interactively, it isn't (so you're okay). I was burned by this also. I think in 2.2 the limits are way too low... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 11:47:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18362 for freebsd-isp-outgoing; Tue, 20 Oct 1998 11:47:30 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18357 for ; Tue, 20 Oct 1998 11:47:29 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id NAA17760; Tue, 20 Oct 1998 13:47:04 -0500 (CDT) Received: from aridius-23.isdn.mke.execpc.com(169.207.66.150) by peak.mountin.net via smap (V1.3) id sma017757; Tue Oct 20 13:46:37 1998 Message-Id: <3.0.3.32.19981020133335.0106947c@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 20 Oct 1998 13:33:35 -0500 To: Paul Stewart , freebsd-isp@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: 3.0 Upgrade Question In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 08:46 AM 10/20/98 -0400, Paul Stewart wrote: >I would first like to thank everyone for their response to my secure >server not working in 3.0-RELEASE.... I shouldn't have played with >fire..:) Since, I have re-installed the server to 2.2.7-RELEASE and >everything is working fine.... thank you. A little fast out of the gate. ;) >On a side note, we have several machines running on 122597-SNAP releases. >They are running just fine except I can't compile UCD-SNMP on them which >is now needed. So, I was thinking of updating them to 3.0-RELEASE. Am I >playing with fire again? I can't take these machines offline for a long >period of time. Can I CVSUP them to the newest kernel trees and remake >the kernel? Is this a safe practice? For myself I've only been reading current for about a month, but there seemed to be problems in cvsup'ing up to 3.0, especially from an older release or even from a 1-2 month old -current. Mainly the problems were related to the aout -> elf issues and buildworld's failing for whatever reasons. I'd pass on this method. >As you can tell, I'm not used to upgrading these machines. They run >currently like a dream but I don't want to fall a LONG ways behind in the >current kernels...:) If planned well you can upgrade them is less than an hour. Generally my preference is to keep the OS and ports on one drive (or set of partitions) and local/user data and such on other drive/partitions. The reason I say drives is that way you can disconnected them for absolute certainty. Liking to start fresh, I either repartition or at least newfs, but only after a double backup. One to tape, the other for config file on a drive/partition that will not be touched during the install. If you go the newfs way, write down or copy your current disklable(s). When you mount the partitions add the newfs flag , so they are redone. Forget the option, but then I like to wipe it clean. Usually to adjust the partition sizes, since it seems like the minimum needs of / have grown slightly. The advantage of keeping mainly the OS and ports on one drive is even clearer if you have a spare server. Then it's a matter of installing, adding ports, and configuring the "new" server, actually a drive, and swapping. Before shutting down both servers for the drive swap it is best to remove the production system from the network and connect it to the upgrade server, which is already configured, and transfer any data/logs over. Do this right and you have less than 30 minutes downtime. Another issue is the ports collection. When doing an upgrade ala fresh install on a production server, the ports are not part of my install. Either I tarball what I need from a system already upgraded, or install it after the reboot when install is finished. That way while the collection is installing, the server config is being set and a kernel is tweaked and ready to install. I vaguely recall what is was like upgrading BSDi, or any OS for that matter and starting fresh seems the best way, but only if you can afford _some_ downtime and it isn't too complex. Never did a drive swap yet, but still keep all but one out of several dozen upgrades to less than an hour. However, my next 2 upgrades are bit more complex with some hardware swapping and in one case a 2nd processor will be added and the system is going to a mirrored drive config with a DPT controller. This will be an almost complete swap with 2 drives being transferred to the new setup along with all the logs. I've planned this out for months and hope to be up and running in less than an hour. The system won't be quite set exactly the way I want, but it will be back online and fully functional. Later on it will be a matter of remotely shuffling some files and eventually removing the old drives. Honestly, I can't recall the last time I used the upgrade function of sysinstall and the longest time spent on an upgrade was less than 2 hours. At first I did try an upgrade (to 2.2.5 at the time), which failed horribly. No real panic since the basic config was copied onto the drive with all the web data, so I just did a full, clean install and updated all the config files with my settings. Not sure how much sysinstall's upgrade function has improved, but it has always had a warning. And with the transition from aout -> elf, I'm not sure how "clean" it is. YMMV, but come upgrade time it really shows how important it is to separate services. Having 2 servers for DNS, mx, and authentication goes far on taking the pressure off while upgrading. Not that there isn't a certain zest to the feeling that an error or 3 may make for a long night. It isn't fun restoring from tape. ;) luck Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 11:47:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18383 for freebsd-isp-outgoing; Tue, 20 Oct 1998 11:47:33 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18371 for ; Tue, 20 Oct 1998 11:47:31 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id NAA17761; Tue, 20 Oct 1998 13:47:04 -0500 (CDT) Received: from aridius-23.isdn.mke.execpc.com(169.207.66.150) by peak.mountin.net via smap (V1.3) id smaa17757; Tue Oct 20 13:46:38 1998 Message-Id: <3.0.3.32.19981020134332.01068fb0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 20 Oct 1998 13:43:32 -0500 To: jason , freebsd-isp@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: Batch installs In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:11 AM 10/20/98 -0400, jason wrote: >I have searched on the freebsd site for a way to do batch installs, >but have come up with nothing. Is there a way to have a file that >states all the things you would like to install, etc to make >installing on several servers easier? What on earth is a "batch install" supposed to do? Most servers are similar, so you could do a "base" system, pre-configure a drive, swap to a system, lay the "base" on the swapped drive and cascade your way to a complete system upgrade, but a few simple scripts and a fresh install would do the same. Personally I don't see any reason why to upgade _every_ system in one day, after all it might get boring after your done.... Or it could be more excitement than you dreamed. Unless you have a requirement that 2 or more systems *must* be running the same OS. Spread them out a bit. It makes for steady work and catches problems when the first is allowed to "season" a bit. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 16:31:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16834 for freebsd-isp-outgoing; Tue, 20 Oct 1998 16:31:25 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from ppc1.cybertime.ch (ppc1.cybertime.ch [194.191.120.136]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA16821 for ; Tue, 20 Oct 1998 16:31:23 -0700 (PDT) (envelope-from pajarola@cybertime.ch) Received: from tiamat.dlc.cybertime.ch by ppc1.cybertime.ch (AIX 4.1/UCB 5.64/4.03) id AA05958; Wed, 21 Oct 1998 01:31:07 +0200 Message-Id: <3.0.32.19981021013050.008553f0@www.dlc.cybertime.ch> X-Sender: pajarola@www.dlc.cybertime.ch X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 21 Oct 1998 01:31:07 +0200 To: Karl Pielorz From: Rico Pajarola Subject: Re: 3.0 Upgrade Question Cc: freebsd-isp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >If you really need UCD-SNMP (which I'll confess I don't really know what it is >- some sort of snmp daemon/service?) - maybe someone can come up with a way of >compiling it on 2.2.7 - unless it's really kernel dependant :( It *is* kernel dependant, that's why you usually have to recompile after every upgrade (whenever something big in the kernel changes). Unfortunately, the port also uses to break at the same time... But I could always make it compile somewho by playing with the CFLAGS and LIBS in the makefiles and shuffling around the includes in the source. iirc it always included stdio *and* stdlib... freebsd doesn't like that. stdio is not needed. Rico To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 20 20:38:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10344 for freebsd-isp-outgoing; Tue, 20 Oct 1998 20:38:02 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10283 for ; Tue, 20 Oct 1998 20:37:55 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id PAA21146; Sun, 18 Oct 1998 15:04:37 -0500 (CDT) Received: from luthien-51.isdn.mke.execpc.com(169.207.65.51) by peak.mountin.net via smap (V1.3) id sma021143; Sun Oct 18 15:04:19 1998 Message-Id: <3.0.3.32.19981018150338.00f2805c@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 18 Oct 1998 15:03:38 -0500 To: Dennis , Bill Vermillion , freebsd-isp@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: Don't bet on 3.0 release In-Reply-To: <3.0.32.19981018114951.00723bc8@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:49 AM 10/18/98 -0400, Dennis wrote: >-RELEASE implies that its ready for the general public. If its still in >BETA, which your comments indicate it is, then it should not >be released. What's the point of doing a release if its not ready? Consider that it is the first release of the 3.x branch. Regardless of the OS or application a major release almost always means new features. Along with new problems. When the last transition from 2.1.x -> 2.2 was happening, I held back for that reason. I'm going to need some of the features in 3.0 very soon, but do realize the risk. For 2.2 I could wait. Don't forget the original problem was with a port, which admittedly they should be fixed or not included. At least they are marked broken if one but checks and reads the fine print. Call it a release with reservations. ;) I don't have any, it's solid enough for my needs, which are not trivial for one server. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 06:13:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13880 for freebsd-isp-outgoing; Wed, 21 Oct 1998 06:13:04 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from oz.phear.net (slwag2p13.ozemail.com.au [203.108.157.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13726; Wed, 21 Oct 1998 06:12:55 -0700 (PDT) (envelope-from jim@phrantic.phear.net) Received: from localhost (jim@localhost) by oz.phear.net (8.8.8/8.8.8) with ESMTP id XAA00310; Wed, 21 Oct 1998 23:00:24 +1000 (EST) (envelope-from jim@phrantic.phear.net) Date: Wed, 21 Oct 1998 23:00:23 +1000 (EST) From: Jim Mock To: freebsd-questions@FreeBSD.ORG cc: freebsd-isp@FreeBSD.ORG Subject: [OFF TOPIC] - new ezine Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry for the off topic post, but I figured this was the best way to get the word out and/or generate interest. I've been putting together a new ezine relating to FreeBSD. It's not in competition with Daemon News, nor will it ever be, I just feel that the more resources that are available, the better off the FreeBSD community will be. What I need now, are contributors. I've already contacted a few of you, and there seems to be an interest from those of you I've contacted. The folks who I haven't contacted, if you're interested in writing an article for it, please contact me. I'm currently planning to have the first issue online for Nov. 1st, as long as I have some articles to publish. I have a few that should be coming to me any day now, but I'd like some more so I can keep the Nov. 1st deadline. If you're interested, you can write for every issue or just one, it really doesn't make any difference to me, but the more articles I have, the more information I'll be able to make available. When the site is completed, it will be viewable at http://freebsd.phear.net/ (it's password protected now and will stay that way until the first issue is put out). As I said, if you're interested in contributing an article or articles, please get in contact with me ASAP. Thanks, Jim |=> Jim Mock [jim@thunder.st0rm.com] [jim@phrantic.phear.net] <=| |=> st0rm Internet Services | A franchise of Triax, Inc. <=| |=> web: http://www.st0rm.com/ | web: http://www.phear.net/ <=| |=> Website Design & Hosting | Wagga Wagga, NSW Australia <=| |=> FreeBSD: The Power to Serve | http://www.freebsd.org/ <=| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 12:50:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01097 for freebsd-isp-outgoing; Wed, 21 Oct 1998 12:50:19 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from compacto.nexos.com.br (ns.nexos.com.br [200.239.191.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00953 for ; Wed, 21 Oct 1998 12:50:00 -0700 (PDT) (envelope-from sandro@compacto.nexos.com.br) Received: from localhost (sandro@localhost) by compacto.nexos.com.br (8.8.8/8.8.8) with SMTP id RAA01183 for ; Wed, 21 Oct 1998 17:49:47 -0200 (BDB) (envelope-from sandro@compacto.nexos.com.br) Date: Wed, 21 Oct 1998 17:49:45 -0200 (BDB) From: Sandro Santos Andrade To: freebsd-isp@FreeBSD.ORG Subject: Comparacao ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ola amigos, Acabei de entrar na lista e tenho algumas duvidas. Preciso realizar algumas configuracoes tais como: nao permitir mais de um acesso simultaneo por usuario e desabilitar temporariamente uma conta. Gostaria de saber quais as vantagens/desvantagens dos principais servidores como radius, ascend-radius e radiusd-cistron e algumas dicas para realizar estas configuracoes. Grato desde ja, [[]]'s, Sandro Santos Andrade ~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 13:07:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03530 for freebsd-isp-outgoing; Wed, 21 Oct 1998 13:07:37 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from compacto.nexos.com.br (ns.nexos.com.br [200.239.191.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03524 for ; Wed, 21 Oct 1998 13:07:32 -0700 (PDT) (envelope-from sandro@compacto.nexos.com.br) Received: from localhost (sandro@localhost) by compacto.nexos.com.br (8.8.8/8.8.8) with SMTP id SAA01235 for ; Wed, 21 Oct 1998 18:07:23 -0200 (BDB) (envelope-from sandro@compacto.nexos.com.br) Date: Wed, 21 Oct 1998 18:07:22 -0200 (BDB) From: Sandro Santos Andrade To: freebsd-isp@FreeBSD.ORG Subject: Comparison for dial up servers ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I have just subscribe this list and I already have some questions. I need to realize some configurations such as: disallow more than one simultaneous access by user and cancel temporarily an account. I would like to know advantages/disadvantages of the wide dial up servers such as radius, ascend-radius, and radiusd-cistron e some hints to reach these configurations. Yours sincerely, Sandro Santos Andrade. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 14:11:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11585 for freebsd-isp-outgoing; Wed, 21 Oct 1998 14:11:07 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11569 for ; Wed, 21 Oct 1998 14:11:04 -0700 (PDT) (envelope-from karl@tdx.com) Received: from tdx.com (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id WAA11315; Wed, 21 Oct 1998 22:09:59 +0100 (BST) Message-ID: <362E4D5C.9503828A@tdx.com> Date: Wed, 21 Oct 1998 22:08:44 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Sandro Santos Andrade CC: freebsd-isp@FreeBSD.ORG Subject: Re: Comparison for dial up servers ... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sandro Santos Andrade wrote: > > Hi all, > > I have just subscribe this list and I already have > some questions. I need to realize some configurations > such as: disallow more than one simultaneous access by > user and cancel Have a look at the 'idled' port (/usr/ports/sysutils/idled) for getting rid of people when there idle, and I beleive it will also stop mulitple PPP logins by the same person? > temporarily an account. The way I temporarily disable an account is to run vipw, find the account in the password file - and add a '*' as the _first_ character of their password... Be careful you don't corrupt their actual password, as there one-way encrypted... If they have a '*' as their first character they cannot log in... > I would like to know advantages/disadvantages > of the wide dial up servers such as radius, ascend-radius, > and radiusd-cistron e some hints to reach these configurations. That's a lot of questions, perhaps a little beyond the scope of FreeBSD-ISP (which is for mainly FreeBSD related topics to do with ISP'ing) - maybe someone will offer some advice though... We don't run Radius here as a server, so I can't really comment... Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 15:12:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18680 for freebsd-isp-outgoing; Wed, 21 Oct 1998 15:12:13 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from amber.eaznet.com (amber.eaznet.com [216.19.20.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18675 for ; Wed, 21 Oct 1998 15:12:12 -0700 (PDT) (envelope-from eddie@eaznet.com) Received: from eaznet.com (admin.eaznet.com [216.19.20.16]) by amber.eaznet.com (8.8.7/8.8.5) with ESMTP id PAA07445 for ; Wed, 21 Oct 1998 15:15:25 -0700 (MST) Message-ID: <362E3C18.3D023385@eaznet.com> Date: Wed, 21 Oct 1998 12:55:04 -0700 From: Eddie Fry X-Mailer: Mozilla 4.06 [en] (Win95; U) MIME-Version: 1.0 To: isp@FreeBSD.ORG Subject: Cyrix MII-300 Processor & FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am thinking about using a Cyrix MII-PR300 CPU to build a FreeBSD server (2.2.7-R). Is this going to work? Any thoughts? -- Eddie Fry EAZNet Internet Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 15:20:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19718 for freebsd-isp-outgoing; Wed, 21 Oct 1998 15:20:56 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from parsons.rh.rit.edu (d111-l052.rh.rit.edu [129.21.111.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19704 for ; Wed, 21 Oct 1998 15:20:50 -0700 (PDT) (envelope-from mfisher@csh.rit.edu) Received: from mfisher (helo=localhost) by parsons.rh.rit.edu with local-esmtp (Exim 2.05 #1) id 0zW6bG-0004Bu-00; Wed, 21 Oct 1998 18:19:26 -0400 Date: Wed, 21 Oct 1998 18:19:26 -0400 (EDT) From: Mike Fisher X-Sender: mfisher@d111-l052.rh.rit.edu To: Karl Pielorz cc: Sandro Santos Andrade , freebsd-isp@FreeBSD.ORG Subject: Re: Comparison for dial up servers ... In-Reply-To: <362E4D5C.9503828A@tdx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 21 Oct 1998, Karl Pielorz wrote: > > temporarily an account. > > The way I temporarily disable an account is to run vipw, find the account in > the password file - and add a '*' as the _first_ character of their > password... Be careful you don't corrupt their actual password, as there > one-way encrypted... > > If they have a '*' as their first character they cannot log in... This is not correct. If the user has setup S/Key authentication or uses non-password based authentication (like .rhosts/.shosts), they do not need a valid password entry -- but they do require a valid shell, since the shell changing capacities of the .login_conf do not currently work. If you want to truly disable an account, do both -- change their shell to /sbin/nologin (or a local alternative) and put the '*' at the beginning of the password field. -- Mike "...check your premises. You will find that one of them is wrong." --Ayn Rand, _Atlas Shrugged_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 16:03:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24157 for freebsd-isp-outgoing; Wed, 21 Oct 1998 16:03:51 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24065 for ; Wed, 21 Oct 1998 16:03:03 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id XAA12358; Wed, 21 Oct 1998 23:59:25 +0100 (BST) Date: Wed, 21 Oct 1998 23:59:25 +0100 (BST) From: Karl Pielorz To: Mike Fisher cc: Karl Pielorz , Sandro Santos Andrade , freebsd-isp@FreeBSD.ORG Subject: Re: Comparison for dial up servers ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 21 Oct 1998, Mike Fisher wrote: > On Wed, 21 Oct 1998, Karl Pielorz wrote: > > > If they have a '*' as their first character they cannot log in... > > This is not correct. If the user has setup S/Key authentication or uses > non-password based authentication (like .rhosts/.shosts), they do not need > a valid password entry -- but they do require a valid shell, since the > shell changing capacities of the .login_conf do not currently work. Granted, but it works fine for PPP and Radius, which is what I thought was being discussed at the time... ;-) > If you want to truly disable an account, do both -- change their shell to > /sbin/nologin (or a local alternative) and put the '*' at the beginning of > the password field. They never have valid shells on our system anyway... But there again, we never have provided shell access... Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 16:25:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27110 for freebsd-isp-outgoing; Wed, 21 Oct 1998 16:25:43 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27103 for ; Wed, 21 Oct 1998 16:25:41 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id SAA23549; Wed, 21 Oct 1998 18:25:08 -0500 (CDT) Received: from klinzhai-1.isdn.mke.execpc.com(169.207.65.129) by peak.mountin.net via smap (V1.3) id sma023541; Wed Oct 21 18:24:41 1998 Message-Id: <3.0.3.32.19981021181951.010e4eb0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 18:19:51 -0500 To: Eddie Fry , isp@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: Cyrix MII-300 Processor & FreeBSD In-Reply-To: <362E3C18.3D023385@eaznet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:55 PM 10/21/98 -0700, Eddie Fry wrote: >I am thinking about using a Cyrix MII-PR300 CPU to build a FreeBSD >server (2.2.7-R). Is this going to work? Any thoughts? I've got a PR200 in one server, which works well. Just dogs out for any number crunching. Tried processing an 800MB log with Analog and it was slowwwww. Go AMD if you don't want to give money to Intel (what they still want for Pentium!). You pay a bit more, but should have better performance, if you need it that is. My server is almost idle with 200K dns hits/day and few hundred e-mails. Just don't plan to process http logs on it. Plenty of memory for such a large log, but too slow. No stability problems. And don't forget: options "NO_F00F_HACK" In your kernel. Didn't bother with any of the other options in LINT, which were for older pre-MII processors. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 17:35:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03869 for freebsd-isp-outgoing; Wed, 21 Oct 1998 17:35:05 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from imap.noc.inc.net (imap.noc.inc.net [204.95.194.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03863 for ; Wed, 21 Oct 1998 17:35:02 -0700 (PDT) (envelope-from steve@inc.net) Received: from inc.net (niki.noc.inc.net [204.95.194.201]) by imap.noc.inc.net (8.9.1/8.8.8) with ESMTP id TAA21133; Wed, 21 Oct 1998 19:34:30 -0500 (CDT) Message-ID: <362E7D95.3EFA03ED@inc.net> Date: Wed, 21 Oct 1998 19:34:29 -0500 From: Steve Kaczkowski Organization: Internet Connect, Inc. X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Jeffrey J. Mountin" CC: Eddie Fry , isp@FreeBSD.ORG Subject: Re: Cyrix MII-300 Processor & FreeBSD References: <3.0.3.32.19981021181951.010e4eb0@207.227.119.2> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Jeffrey J. Mountin" wrote: > > At 12:55 PM 10/21/98 -0700, Eddie Fry wrote: > >I am thinking about using a Cyrix MII-PR300 CPU to build a FreeBSD > >server (2.2.7-R). Is this going to work? Any thoughts? > I'd stick with either Intel or AMD, considering how CHEAP their chips are why would you want to get anything else.. -- Steve Kaczkowski Internet Connect, Inc. steve@inc.net (414)476-ICON x12 http://www.inc.net FAX(414)476-2403 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 18:31:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08890 for freebsd-isp-outgoing; Wed, 21 Oct 1998 18:31:17 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from electric.tbe.net (electric.tbe.net [207.99.115.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA08885 for ; Wed, 21 Oct 1998 18:31:16 -0700 (PDT) (envelope-from gary@tbe.net) Received: (qmail 22467 invoked from network); 22 Oct 1998 01:30:45 -0000 Received: from electric.tbe.net (gary@207.99.115.10) by electric.tbe.net with SMTP; 22 Oct 1998 01:30:45 -0000 Date: Wed, 21 Oct 1998 21:30:44 -0400 (EDT) From: "Gary D. Margiotta" To: Steve Kaczkowski cc: "Jeffrey J. Mountin" , Eddie Fry , isp@FreeBSD.ORG Subject: Re: Cyrix MII-300 Processor & FreeBSD In-Reply-To: <362E7D95.3EFA03ED@inc.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just bought an AMD K2-266 3D, with a Tyan 100Mhz board and 1 Mb of cache... Thing _screams_ for $350 (128 Megs 100Mhz SDRAM incl.). I'd reccommend going the AMD route first over Cyrix, but I'd definitely pick either over any Intel chip for the price/performance, all except for the higher end math-intensive functions... The Intels still are best there... We used nothing but the older Cyrix chips, regular and MMX, up to 233, in our old servers. Well outperformed the equivalent Pentium, but it did still leave a little to be desired when doing higher end math, like log file analyzing, etc. For that, we had a PPRo, and that was more than enough. ______________________________________________________________ -Gary Margiotta Voice: (973) 835-9696 TBE Internet Services Fax: (973) 835-2133 http://www.tbe.net E-Mail: gary@tbe.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 18:42:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10264 for freebsd-isp-outgoing; Wed, 21 Oct 1998 18:42:41 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10249 for ; Wed, 21 Oct 1998 18:42:38 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id UAA23970; Wed, 21 Oct 1998 20:42:11 -0500 (CDT) Received: from klinzhai-1.isdn.mke.execpc.com(169.207.65.129) by peak.mountin.net via smap (V1.3) id sma023968; Wed Oct 21 20:41:47 1998 Message-Id: <3.0.3.32.19981021203653.010d39e8@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 20:36:53 -0500 To: Steve Kaczkowski From: "Jeffrey J. Mountin" Subject: Re: Cyrix MII-300 Processor & FreeBSD Cc: isp@FreeBSD.ORG In-Reply-To: <362E7D95.3EFA03ED@inc.net> References: <3.0.3.32.19981021181951.010e4eb0@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 07:34 PM 10/21/98 -0500, Steve Kaczkowski wrote: >I'd stick with either Intel or AMD, considering how CHEAP their chips >are why would you want to get anything else.. About $70 for a MII-300 vs $110 for K6-2 300. Not much really. Unless Cyrix were to do something radical I _never_ plan to purchase one again. Still it does what I need and was a good buy at the time for one of my workstations. Hmmm... and it's _still_ in my production server. How ironic. But I'm slow to upgrade hardware when it meets the need. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 19:14:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13342 for freebsd-isp-outgoing; Wed, 21 Oct 1998 19:14:13 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13335 for ; Wed, 21 Oct 1998 19:14:12 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id VAA24148; Wed, 21 Oct 1998 21:13:41 -0500 (CDT) Received: from klinzhai-1.isdn.mke.execpc.com(169.207.65.129) by peak.mountin.net via smap (V1.3) id sma024146; Wed Oct 21 21:13:39 1998 Message-Id: <3.0.3.32.19981021210843.0109bc1c@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 21:08:43 -0500 To: "Gary D. Margiotta" From: "Jeffrey J. Mountin" Subject: Re: Cyrix MII-300 Processor & FreeBSD Cc: isp@FreeBSD.ORG In-Reply-To: References: <362E7D95.3EFA03ED@inc.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09:30 PM 10/21/98 -0400, Gary D. Margiotta wrote: >Just bought an AMD K2-266 3D, with a Tyan 100Mhz board and 1 Mb of >cache... Thing _screams_ for $350 (128 Megs 100Mhz SDRAM incl.). I'd >reccommend going the AMD route first over Cyrix, but I'd definitely pick >either over any Intel chip for the price/performance, all except for the >higher end math-intensive functions... The Intels still are best there... Super7 is a good route. They are more stable than before. My next board may be a Slot A (not 1) and the K7 or maybe a Cascades (crossbreed of the Xeon and Celeron). Depends on what happens next year. Work/play systems... for my use. ;) Anyone running a dual CPU AMD setup? No clue how well they work, but with the PPro the L2 runs at clock, not 66/100 for 7/Super7 or 1/2 for PII. Forget the Xeon period. For a server you can't beat a dual-PPro 166. Forget the 180 and 200 with 256K L2 and why pay 4x for the 200-512. Newer ATX boards allow you to overclock too. Anyways, I'd bet I can meet or beat your price/performance with Celeron 333a, board, memory for around $450. The clinch is it running at 500MHz. Ok, I do have better memory which adds about $50 to the price (for ECC add another $100). It's stable and reliable. AMD/Cyrix don't overclock, but I've been doing for years with Intel in server environments. Longer for my personal systems. Call me crazy, but I have yet to cook a CPU. An Asus T2P4 running an 83MHz bus was a killer news server. 8-) >We used nothing but the older Cyrix chips, regular and MMX, up to 233, in >our old servers. Well outperformed the equivalent Pentium, but it did >still leave a little to be desired when doing higher end math, like log >file analyzing, etc. For that, we had a PPRo, and that was more than >enough. Integer is poor on Cyrix, FPU is really poor. YMMV, but I did some testing. Day to day I found my PR200 quite acceptable, but it was noticably slow doing spreadsheets. Far slower than the P166 it replaced. In fact my P75 did better. Quite sad really. Hopefully the K7 will live up to expectations. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 19:32:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15482 for freebsd-isp-outgoing; Wed, 21 Oct 1998 19:32:30 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from portal.net.au (galley.portal.net.au [202.12.71.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15467 for ; Wed, 21 Oct 1998 19:32:26 -0700 (PDT) (envelope-from matt@portal.net.au) Received: (from matt@localhost) by portal.net.au (8.8.8/8.8.8) id MAA00858 for freebsd-isp@freebsd.org; Thu, 22 Oct 1998 12:01:54 +0930 (CST) From: Matt Baker Message-Id: <199810220231.MAA00858@portal.net.au> Subject: PPPD stats clearing To: freebsd-isp@FreeBSD.ORG Date: Thu, 22 Oct 1998 12:01:53 +0930 (CST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just wondering if someone has an idea on how to clear the interface stats for people connecting via pppd. At the moment I have a program which when the user logs off, records the number of bytes that they used. The problem I'm finding is that the interface doesn't seem to have it's stats cleared when the next user logs onto that port. Any ideas on how I could clear inte interface? thanks, --matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 20:41:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21379 for freebsd-isp-outgoing; Wed, 21 Oct 1998 20:41:27 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from portal.net.au (galley.portal.net.au [202.12.71.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21374 for ; Wed, 21 Oct 1998 20:41:24 -0700 (PDT) (envelope-from matt@portal.net.au) Received: (from matt@localhost) by portal.net.au (8.8.8/8.8.8) id NAA01356; Thu, 22 Oct 1998 13:10:50 +0930 (CST) From: Matt Baker Message-Id: <199810220340.NAA01356@portal.net.au> Subject: Re: PPPD stats clearing To: tomthai@future.net (Tom T. Thai) Date: Thu, 22 Oct 1998 13:10:50 +0930 (CST) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: from "Tom T. Thai" at Oct 21, 98 10:25:44 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yes, eventually I want to goto a radius style way of doing this, but for the moment I dont' really want to affect the operation too much. (I don't believe that the radius aware pppd is yet working?) For this reason I thought I'ld just have a simple program that just logged the bytes used when the user disconnected. I've hacked a pppstat's program to just give me the info for a particular port. --matt > > I'm not sure if this option would work for you. Maybe you can use a > patched pppd with radius and use a radius server? that way, you can keep > track of bytes in and out? > > > .............. .................................... > Thomas T. Thai Infomedia Interactive Communications > tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 > > > On Thu, 22 Oct 1998, Matt Baker wrote: > > > Just wondering if someone has an idea on how to clear the interface > > stats for people connecting via pppd. > > At the moment I have a program which when the user logs off, records > > the number of bytes that they used. The problem I'm finding is > > that the interface doesn't seem to have it's stats cleared > > when the next user logs onto that port. > > Any ideas on how I could clear inte interface? > > > > > > thanks, > > > > --matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-isp" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 20:47:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22273 for freebsd-isp-outgoing; Wed, 21 Oct 1998 20:47:09 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from dream.future.net (future.net [204.130.134.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22265 for ; Wed, 21 Oct 1998 20:47:08 -0700 (PDT) (envelope-from tomthai@future.net) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.6/8.8.6) with SMTP id WAA22166; Wed, 21 Oct 1998 22:38:21 -0500 (CDT) Date: Wed, 21 Oct 1998 22:38:21 -0500 (CDT) From: "Tom T. Thai" To: Matt Baker cc: freebsd-isp@FreeBSD.ORG Subject: Re: PPPD stats clearing In-Reply-To: <199810220340.NAA01356@portal.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org pppd with radius has been around for a while and it works rather well. .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 On Thu, 22 Oct 1998, Matt Baker wrote: > Yes, eventually I want to goto a radius style way of doing this, > but for the moment I dont' really want to affect the operation too > much. (I don't believe that the radius aware pppd is yet working?) > For this reason I thought I'ld just have a simple program that just > logged the bytes used when the user disconnected. I've hacked a > pppstat's program to just give me the info for a particular port. > > --matt > > > > > I'm not sure if this option would work for you. Maybe you can use a > > patched pppd with radius and use a radius server? that way, you can keep > > track of bytes in and out? > > > > > > .............. .................................... > > Thomas T. Thai Infomedia Interactive Communications > > tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 > > > > > > On Thu, 22 Oct 1998, Matt Baker wrote: > > > > > Just wondering if someone has an idea on how to clear the interface > > > stats for people connecting via pppd. > > > At the moment I have a program which when the user logs off, records > > > the number of bytes that they used. The problem I'm finding is > > > that the interface doesn't seem to have it's stats cleared > > > when the next user logs onto that port. > > > Any ideas on how I could clear inte interface? > > > > > > > > > thanks, > > > > > > --matt > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-isp" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 21 23:00:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00675 for freebsd-isp-outgoing; Wed, 21 Oct 1998 23:00:08 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from is2.net.ohio-state.edu (is2.net.ohio-state.edu [128.146.48.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA00660 for ; Wed, 21 Oct 1998 23:00:06 -0700 (PDT) (envelope-from maf@dev1.net.ohio-state.edu) Received: (qmail 2945 invoked from network); 22 Oct 1998 05:59:36 -0000 Received: from dev1.net.ohio-state.edu (128.146.222.3) by is2.net.ohio-state.edu with SMTP; 22 Oct 1998 05:59:36 -0000 Received: (qmail 11624 invoked by uid 4454); 22 Oct 1998 05:59:36 -0000 Message-ID: <19981022015936.A10914@net.ohio-state.edu> Date: Thu, 22 Oct 1998 01:59:36 -0400 From: Mark Fullmer To: jason , freebsd-isp@FreeBSD.ORG Subject: Re: Batch installs References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: ; from jason on Tue, Oct 20, 1998 at 11:11:43AM -0400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 20, 1998 at 11:11:43AM -0400, jason wrote: > I have searched on the freebsd site for a way to do batch installs, > but have come up with nothing. Is there a way to have a file that > states all the things you would like to install, etc to make > installing on several servers easier? Custom boot floppy and sdist. For a new install/upgrade the box boots with a minimal floppy that NFS mounts /usr and a configuration directory specific to the machine from the master server. The configuration file tells it how to setup the disk(s), file systems, and copy in a /, /usr, and /var. Once the file systems are in place config files get copied over, a ssh host key generated, etc. To keep it up to date, the master server dists out /usr to all the clients. Configuration changes like rc.conf are also disted out. Software always gets installed on the master and disted out. Use sym links to maintain multiple versions of the same package in /usr/local. The one important thing to remember is not to store local machine state in /usr, ie /usr/local/etc/configfile won't work because there's no easy way to keep separate files on the master for each client. The FreeBSD ports collection has always been a problem because of this... I have about 30 or so fbsd boxes all synch'd to 1 running like this. -- mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 22 05:55:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27887 for freebsd-isp-outgoing; Thu, 22 Oct 1998 05:55:39 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mx.iki.rssi.ru (mx.iki.rssi.ru [193.232.212.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27881 for ; Thu, 22 Oct 1998 05:55:36 -0700 (PDT) (envelope-from Andrew.Karjagin@tdis.gctc.rssi.ru) Received: from tdis.gctc.rssi.ru (tdis.gctc.rssi.ru [193.232.26.70]) by mx.iki.rssi.ru (8.9.1/8.9.1) with SMTP id OAA01389 for ; Thu, 22 Oct 1998 14:22:12 +0400 (MSD) Received: from tdis.gctc.rssi.ru by tdis.gctc.rssi.ru (SMI-8.6/SMI-SVR4) id OAA02374; Thu, 22 Oct 1998 14:15:48 +0400 Message-ID: <362F05D3.1DC60039@tdis.gctc.rssi.ru> Date: Thu, 22 Oct 1998 14:15:48 +0400 From: "Andrew A.Karjagin" Organization: Gagarin Cosmonaut Training Center X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: "isp@FreeBSD.ORG" Subject: Lised modem line Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, all! Help me, please, to configure a remote access to FreeBSD 2.2.6 box by lised (stand out, distinguish) telephone line. I have two Courier modems, FreeBSD box as server, Windows box as client and I want to use a SLIP protocol between hosts. The options at the internal modem RAM are set for the lised line, getty is contacted modem on FreeBSD box and modems are contacted themselves, but getty don't put a terminal window for client, as it do in case of standard telephone line. Thank you for help! -- Best wishes Andrew A.Karjagin Gagarin Cosmonaut Training Center, Star Town, Russia http://tdis.gctc.rssi.ru/richi (only in Russian) Problem with decoding of Cyr letters? Go http://www.mtrros.msk.ru/decode.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 22 06:52:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03480 for freebsd-isp-outgoing; Thu, 22 Oct 1998 06:52:56 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from carp.gbr.epa.gov (carp.gbr.epa.gov [204.46.159.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03475 for ; Thu, 22 Oct 1998 06:52:53 -0700 (PDT) (envelope-from mjenkins@carp.gbr.epa.gov) Received: (from mjenkins@localhost) by carp.gbr.epa.gov (8.8.8/8.8.8) id IAA00367; Thu, 22 Oct 1998 08:52:20 -0500 (CDT) (envelope-from mjenkins) Date: Thu, 22 Oct 1998 08:52:20 -0500 (CDT) From: Mike Jenkins Message-Id: <199810221352.IAA00367@carp.gbr.epa.gov> To: matt@portal.net.au Subject: Re: PPPD stats clearing Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: <199810220231.MAA00858@portal.net.au> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Just wondering if someone has an idea on how to clear the interface > stats for people connecting via pppd. > At the moment I have a program which when the user logs off, records > the number of bytes that they used. The problem I'm finding is > that the interface doesn't seem to have it's stats cleared > when the next user logs onto that port. > Any ideas on how I could clear inte interface? Take a before snapshot in /etc/ppp/ip-up and an after snapshot in /etc/ppp/ip-down, and then subtract the two. Seems like there should be a -c option to netstat for clearing counters. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 22 08:24:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10771 for freebsd-isp-outgoing; Thu, 22 Oct 1998 08:24:05 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from amber.eaznet.com (amber.eaznet.com [216.19.20.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10766 for ; Thu, 22 Oct 1998 08:24:03 -0700 (PDT) (envelope-from eddie@eaznet.com) Received: from eaznet.com (admin.eaznet.com [216.19.20.16]) by amber.eaznet.com (8.8.7/8.8.5) with ESMTP id IAA15669; Thu, 22 Oct 1998 08:27:13 -0700 (MST) Message-ID: <362F2DF0.DA8EDC7A@eaznet.com> Date: Thu, 22 Oct 1998 06:06:56 -0700 From: Eddie Fry X-Mailer: Mozilla 4.06 [en] (Win95; U) MIME-Version: 1.0 To: "Jeffrey J. Mountin" CC: isp@FreeBSD.ORG Subject: Re: Cyrix MII-300 Processor & FreeBSD References: <3.0.3.32.19981021181951.010e4eb0@207.227.119.2> <3.0.3.32.19981021203653.010d39e8@207.227.119.2> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wanted a K6, but with the price cuts coming, my suppliers won't get me one. So, I bought a Cyrix instead. I guess I can always pull it in a month and replace it with, what will probably be a cheaper, K6. When are the K7's coming out? I've read about them, but thought they were a ways off yet. Eddie Jeffrey J. Mountin wrote: > At 07:34 PM 10/21/98 -0500, Steve Kaczkowski wrote: > >I'd stick with either Intel or AMD, considering how CHEAP their chips > >are why would you want to get anything else.. > > About $70 for a MII-300 vs $110 for K6-2 300. Not much really. Unless > Cyrix were to do something radical I _never_ plan to purchase one again. > > Still it does what I need and was a good buy at the time for one of my > workstations. Hmmm... and it's _still_ in my production server. How ironic. > > But I'm slow to upgrade hardware when it meets the need. > > Jeff Mountin - Unix Systems TCP/IP networking > jeff@mountin.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message -- Eddie Fry EAZNet Internet Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 22 09:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19461 for freebsd-isp-outgoing; Thu, 22 Oct 1998 09:46:09 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from carp.gbr.epa.gov (carp.gbr.epa.gov [204.46.159.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19456 for ; Thu, 22 Oct 1998 09:46:07 -0700 (PDT) (envelope-from mjenkins@carp.gbr.epa.gov) Received: (from mjenkins@localhost) by carp.gbr.epa.gov (8.8.8/8.8.8) id LAA00613; Thu, 22 Oct 1998 11:44:20 -0500 (CDT) (envelope-from mjenkins) Date: Thu, 22 Oct 1998 11:44:20 -0500 (CDT) From: Mike Jenkins Message-Id: <199810221644.LAA00613@carp.gbr.epa.gov> To: Andrew.Karjagin@tdis.gctc.rssi.ru Subject: Re: Lised modem line Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: <362F05D3.1DC60039@tdis.gctc.rssi.ru> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Date: Thu, 22 Oct 1998 14:15:48 +0400 > From: "Andrew A.Karjagin" > > Help me, please, to configure a remote access to FreeBSD 2.2.6 box by > lised (stand out, distinguish) telephone line. > I have two Courier modems, FreeBSD box as server, Windows box as client > and I want to use a SLIP protocol between hosts. > The options at the internal modem RAM are set for the lised line, getty > is contacted modem on FreeBSD box and modems are > contacted themselves, but getty don't put a terminal window for client, > as it do in case of standard telephone line. Thank you for help! The default dialin devices (ttyd?) expect carrier. Maybe the modem is not providing the carrier signal. Tell FreeBSD to ignore modem signals on the device with an stty command on the "initial state" device: # stty -f /dev/ttyid0 clocal See sio(4) and stty(1). Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 22 10:19:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24240 for freebsd-isp-outgoing; Thu, 22 Oct 1998 10:19:28 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from obiwan.TerraNova.net (obiwan.TerraNova.net [205.152.191.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24235 for ; Thu, 22 Oct 1998 10:19:25 -0700 (PDT) (envelope-from bofh@terranova.net) Received: from terranova.net (tog@guenhwyvar.TerraNova.net [205.152.191.4]) by obiwan.TerraNova.net (8.9.1a/TNN/3.1) with ESMTP id NAA12264; Thu, 22 Oct 1998 13:18:40 -0400 (EDT) Message-ID: <362F6847.7F7E4D0B@terranova.net> Date: Thu, 22 Oct 1998 13:15:51 -0400 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Eddie Fry CC: isp@FreeBSD.ORG Subject: Re: Cyrix MII-300 Processor & FreeBSD References: <3.0.3.32.19981021181951.010e4eb0@207.227.119.2> <3.0.3.32.19981021203653.010d39e8@207.227.119.2> <362F2DF0.DA8EDC7A@eaznet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eddie Fry wrote: > > I wanted a K6, but with the price cuts coming, my suppliers won't get me one. > So, I bought a Cyrix instead. I guess I can always pull it in a month and > replace it with, what will probably be a cheaper, K6. When are the K7's coming > out? I've read about them, but thought they were a ways off yet. "First half of '99" As opposed to the K6-3's "1st quarter '99" I'll take a K6-3 or two myself when it comes out.. it's not going to be really expensive or anything, so why wait? Perhaps this discussion should be moved to -chat pretty soon. -T -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- "By the time they had diminished from 50 to 8, the other dwarves began to suspect 'Hungry'..." -- Gary Larson, "The Far Side" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 22 11:27:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04663 for freebsd-isp-outgoing; Thu, 22 Oct 1998 11:27:01 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from out5.ibm.net (out5.ibm.net [165.87.194.243]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04652 for ; Thu, 22 Oct 1998 11:26:59 -0700 (PDT) (envelope-from dwilde1@ibm.net) Received: from ibm.net (slip-32-100-79-203.ca.us.ibm.net [32.100.79.203]) by out5.ibm.net (8.8.5/8.6.9) with ESMTP id SAA18146 for ; Thu, 22 Oct 1998 18:26:18 GMT Message-ID: <362F77DC.4177F930@ibm.net> Date: Thu, 22 Oct 1998 11:22:20 -0700 From: Don Wilde X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: freebsd-isp@FreeBSD.ORG Subject: local ISP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, folks! I need a simple site hosted with CGI and eventually DB capability, and of course I want it to be FreeBSD-based. I like working with the net provider 'softaware.com', are any of you co-located there in Marina Del Rey, CA? Alternatively, are any of you in Albuquerque, NM? I realize I don't need physical access, so anybody else is also welcome to respond, but I'd like to know the people at my ISP on a personal basis. -- oooOOO O O O o * * * * * * o ___ _________ _________ _________ ___==__ V_=_=_DW ===--- Don Wilde [dwilde1 @ ibm.net] [ = = ] /oo0000oo-oo--oo-ooo---ooo-ooo---ooo-ooo---ooo-oo---oo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 22 14:34:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04349 for freebsd-isp-outgoing; Thu, 22 Oct 1998 14:34:24 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from ns2.interlinks.net (ns2.interlinks.net [207.107.160.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04338; Thu, 22 Oct 1998 14:34:20 -0700 (PDT) (envelope-from bill@interlinks.net) Received: from localhost (bill@localhost) by ns2.interlinks.net (8.9.1/8.8.8) with ESMTP id RAA04990; Thu, 22 Oct 1998 17:26:53 -0400 (EDT) Date: Thu, 22 Oct 1998 17:26:52 -0400 (EDT) From: Bill Sandiford To: freebsd-bugs@FreeBSD.ORG cc: freebsd-isp@FreeBSD.ORG Subject: FreeBSD 3.0 Release and pw command - Potential Bug? (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We are having a problem with FreeBSD 3.0 Release and it's associated pw command. We have scripts that used to work perfectly in the 2.2.x line. The script still works perfectly when we run it manually as root (logged in at the terminal) however when cron executes the script, the pw commands in the script don't work. We are executing the script using the crontab for root. We know that the script is executing because some of the other commands in the script are happening and working. The script is designed to add a new user to our system and the line with pw looks something like this : echo password | pw useradd username -h 0 -c "Full Name" -g group -u uid -m -d homedir obviously we substitute a correct numeric id for uid and proper groupname for group, etc. We are not sure if this is a problem with our system or a bug with the pw command that is in the 3.0 release...we have also tried invoking the script from and inetd process as well.....we have tried this script on 3 different systems and it doesn't work on any of them except when invoked manually. Any help please!!! ------------------------------------------ Bill Sandiford Jr. - Systems Administrator Interlinks - http://www.interlinks.net sysop@interlinks.net - bill@interlinks.net (905)404-0810 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 22 15:39:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13947 for freebsd-isp-outgoing; Thu, 22 Oct 1998 15:39:13 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13918 for ; Thu, 22 Oct 1998 15:38:41 -0700 (PDT) (envelope-from root@swimsuit.internet.dk) Received: from localhost (localhost [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id AAA01705 for ; Fri, 23 Oct 1998 00:38:03 +0200 (CEST) (envelope-from root@swimsuit.internet.dk) Date: Fri, 23 Oct 1998 00:38:03 +0200 (CEST) From: Leif Neland To: freebsd-isp@FreeBSD.ORG Subject: route changes erratically (routed) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have 2 portmasters (PM2), several servers, a cisco to the world, and a firewall to the internal network. The cisco is default gateway The servers and portmasters are on one class C, the dialins are on another class C. Because some users have fixed ip, but can dial in on either of the portmasters, I run routed on all servers, and the portmasters seem to announce on which portmaster the customer is, so the route gets changed to the right portmaster. The traceroute should then go from server to pm1 or pm2 to customer. However, often the route changes so it goes server->cisco->pm->client or server->firewall->pm->client or even server->cisco->(router at our uplink)->cisco->(router at our uplink) etc. If I constantly pings the client, I gets pauses where the pings are lost. What do I do wrong? Shouldn't I use routed on the servers, but only route default gateway to the cisco, and let it handle the pm1/pm2 route changes? Or should I have one server running routed? or gated? or what? Help!!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 22 15:44:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14907 for freebsd-isp-outgoing; Thu, 22 Oct 1998 15:44:29 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from lodgenet.com (cline.lodgenet.com [204.124.122.251]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14892; Thu, 22 Oct 1998 15:44:24 -0700 (PDT) (envelope-from johnp@lodgenet.com) Received: from milo.lodgenet.com (milo.lodgenet.com [10.0.122.42]) by lodgenet.com (8.7.5/8.7.3) with ESMTP id RAA04562; Thu, 22 Oct 1998 17:43:52 -0500 Received: from milo.lodgenet.com (localhost [127.0.0.1]) by milo.lodgenet.com (8.9.1/8.9.1) with ESMTP id RAA03187; Thu, 22 Oct 1998 17:43:34 -0500 (CDT) (envelope-from johnp@milo.lodgenet.com) Message-Id: <199810222243.RAA03187@milo.lodgenet.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Sandiford cc: freebsd-bugs@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? (fwd) In-reply-to: Your message of "Thu, 22 Oct 1998 17:26:52 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 17:43:34 -0500 From: John Prince Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am not sure what your crontabs file looks like, however.. `pw' is locate in /usr/sbin.. Check your path.. Better yet, include it in your script. --John Bill Sandiford writes: > > We are having a problem with FreeBSD 3.0 Release and it's associated pw > command. We have scripts that used to work perfectly in the 2.2.x line. > The script still works perfectly when we run it manually as root (logged > in at the terminal) however when cron executes the script, the pw commands > in the script don't work. We are executing the script using the crontab > for root. We know that the script is executing because some of the > other commands in the script are happening and working. The script is > designed to add a new user to our system and the line with pw looks > something like this : > > echo password | pw useradd username -h 0 -c "Full Name" -g group -u uid -m -d homedir > > obviously we substitute a correct numeric id for uid and proper groupname > for group, etc. > > We are not sure if this is a problem with our system or a bug with the pw > command that is in the 3.0 release...we have also tried invoking the > script from and inetd process as well.....we have tried this script on 3 > different systems and it doesn't work on any of them except when invoked > manually. > > Any help please!!! > > ------------------------------------------ > Bill Sandiford Jr. - Systems Administrator > Interlinks - http://www.interlinks.net > sysop@interlinks.net - bill@interlinks.net > (905)404-0810 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 22 19:58:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11736 for freebsd-isp-outgoing; Thu, 22 Oct 1998 19:58:10 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA11719; Thu, 22 Oct 1998 19:58:07 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <430465(4)>; Thu, 22 Oct 1998 19:57:34 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177539>; Thu, 22 Oct 1998 19:57:28 -0700 To: Bill Sandiford cc: freebsd-bugs@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? (fwd) In-reply-to: Your message of "Thu, 22 Oct 98 14:26:52 PDT." Date: Thu, 22 Oct 1998 19:57:25 PDT From: Bill Fenner Message-Id: <98Oct22.195728pdt.177539@crevenia.parc.xerox.com> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is /usr/sbin in your $PATH when using cron? (Check the X-Cron-Env: headers of the email that cron sends you). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Oct 23 01:03:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05264 for freebsd-isp-outgoing; Fri, 23 Oct 1998 01:03:03 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA05259 for ; Fri, 23 Oct 1998 01:03:01 -0700 (PDT) (envelope-from jesper@freesbee.t.dk) Received: (qmail 8711 invoked by uid 1001); 23 Oct 1998 08:02:23 -0000 Date: Fri, 23 Oct 1998 10:02:23 +0200 From: Jesper Skriver To: Leif Neland Cc: freebsd-isp@FreeBSD.ORG Subject: Re: route changes erratically (routed) Message-ID: <19981023100223.G8559@skriver.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i In-Reply-To: ; from Leif Neland on Fri, Oct 23, 1998 at 12:38:03AM +0200 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Oct 23, 1998 at 12:38:03AM +0200, Leif Neland wrote: > We have 2 portmasters (PM2), several servers, a cisco to the world, and a > firewall to the internal network. > > The cisco is default gateway > > The servers and portmasters are on one class C, the dialins are on another > class C. > > Because some users have fixed ip, but can dial in on either of the > portmasters, I run routed on all servers, and the portmasters seem to > announce on which portmaster the customer is, so the route gets changed to > the right portmaster. > > The traceroute should then go from server to pm1 or pm2 to customer. > > However, often the route changes so it goes > server->cisco->pm->client or > server->firewall->pm->client or even > server->cisco->(router at our uplink)->cisco->(router at our uplink) etc. > > If I constantly pings the client, I gets pauses where the pings are lost. > > What do I do wrong? Shouldn't I use routed on the servers, but only route > default gateway to the cisco, and let it handle the pm1/pm2 route changes? > Or should I have one server running routed? or gated? or what? You're probabaly using RIP (version1), and it doesn't support CIDR => Lots of trouble. What I would do was something like this. Let all your servers and the firewall have a static default route to the cisco router, and not run routed or gated on these. Enable OSPF on both the cisco and the portmasters, OSPF has sigificant advantages over RIP, it supports CIDR among other things. RIP version2 could also solve your problem. If you need help with this Tele Danmark has consultants that can help you, but it'll cost you ... /Jesper -- Jesper Skriver (JS249-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Oct 23 08:45:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11512 for freebsd-isp-outgoing; Fri, 23 Oct 1998 08:45:33 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11507 for ; Fri, 23 Oct 1998 08:45:32 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id IAA17027; Fri, 23 Oct 1998 08:33:59 -0700 (PDT) (envelope-from dhw) Date: Fri, 23 Oct 1998 08:33:59 -0700 (PDT) From: David Wolfskill Message-Id: <199810231533.IAA17027@pau-amma.whistle.com> To: jesper@skriver.dk, root@swimsuit.internet.dk Subject: Re: route changes erratically (routed) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: <19981023100223.G8559@skriver.dk> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Date: Fri, 23 Oct 1998 10:02:23 +0200 >From: Jesper Skriver >Enable OSPF on both the cisco and the portmasters, OSPF has sigificant >advantages over RIP, it supports CIDR among other things. RIP version2 >could also solve your problem. Except that the Lucent RABU (formerly Livingston) folks looked at RIPv2 (after they already supported OSPF), and decided against doing RIPv2 in the PortMasters. (At least, this is what I recall having read in discussions in the portmaster-users mailiang list.) So OSPF would seem to be the way to go. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Oct 23 14:12:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10755 for freebsd-isp-outgoing; Fri, 23 Oct 1998 14:12:54 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10750 for ; Fri, 23 Oct 1998 14:12:52 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id QAA01569; Fri, 23 Oct 1998 16:11:03 -0500 (CDT) Received: from klinzhai-109.isdn.mke.execpc.com(169.207.65.237) by peak.mountin.net via smap (V1.3) id sma001567; Fri Oct 23 16:11:01 1998 Message-Id: <3.0.3.32.19981023160648.00704f04@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 23 Oct 1998 16:06:48 -0500 To: David Wolfskill , jesper@skriver.dk, root@swimsuit.internet.dk From: "Jeffrey J. Mountin" Subject: Re: route changes erratically (routed) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: <199810231533.IAA17027@pau-amma.whistle.com> References: <19981023100223.G8559@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 08:33 AM 10/23/98 -0700, David Wolfskill wrote: >>Date: Fri, 23 Oct 1998 10:02:23 +0200 >>From: Jesper Skriver > >>Enable OSPF on both the cisco and the portmasters, OSPF has sigificant >>advantages over RIP, it supports CIDR among other things. RIP version2 >>could also solve your problem. > >Except that the Lucent RABU (formerly Livingston) folks looked at RIPv2 >(after they already supported OSPF), and decided against doing RIPv2 in >the PortMasters. (At least, this is what I recall having read in >discussions in the portmaster-users mailiang list.) So OSPF would seem >to be the way to go. You are correct about Livingston and RIPv2 and I agree with the OSPF. Almost have some info pages for this setup ready. They are more geared to OSPF with the PM3 (there will be some Cisco info as well), which needs 23/24/46/48 IPs. That in itself is cause for headache unless you use OSPF. Even so, with OSPF you can aggregate the routes further with a little planning, which I can demonstrate with 5 PM3's on a /24 going from 33 -> 18 routes, making for a cleaner, smaller table in the Cisco. Need to clean it up a bit first. Anyone interested can reply directly. cheers! Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Oct 23 18:08:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29938 for freebsd-isp-outgoing; Fri, 23 Oct 1998 18:08:46 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from trantor.galaxia.com (terminus.galaxia.com [204.255.210.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29931 for ; Fri, 23 Oct 1998 18:08:43 -0700 (PDT) (envelope-from dave@galaxia.com) Received: from localhost (dave@localhost) by trantor.galaxia.com (8.8.8/8.8.7) with ESMTP id VAA26484 for ; Fri, 23 Oct 1998 21:08:07 -0400 (EDT) (envelope-from dave@galaxia.com) Date: Fri, 23 Oct 1998 21:08:07 -0400 (EDT) From: "David H. Brierley" To: freebsd-isp@FreeBSD.ORG Subject: Looking for small newsfeed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I run a small ISP located in Rhode Island (east coast) and I just had my old newsfeed site pulled out from underneath me. Can someone please help me? We currently only have a handfull of customers that want to access news so I had been running a caching proxy server on one of my machines and I would like to be able to continue doing that. This makes me look like a single interactive user to your server. Before you say "contact your service provider" and get them to give you a feed, they are the ones that yanked my feed on me. They are willing to give me a full blown feed using nntp batching, but they don't want to allow the interactive stuff that the proxy server was using. I don't want the full blown feed because I don't want news to chew up all of my available bandwidth, not to mention all of my disk space. -- David H. Brierley dave@galaxia.com / dave@aiconnect.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Oct 24 12:23:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02613 for freebsd-isp-outgoing; Sat, 24 Oct 1998 12:23:06 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gull.prod.itd.earthlink.net (gull.prod.itd.earthlink.net [207.217.120.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02605 for ; Sat, 24 Oct 1998 12:23:02 -0700 (PDT) (envelope-from ashton@ilovejesus.com) From: ashton@ilovejesus.com Received: from wizkid (ip46.dublin3.oh.pub-ip.psi.net [38.12.92.46]) by gull.prod.itd.earthlink.net (8.8.7/8.8.5) with SMTP id MAA11687 for freebsd-isp@FreeBSD.ORG; Sat, 24 Oct 1998 12:22:28 -0700 (PDT) Date: Sat, 24 Oct 1998 12:22:28 -0700 (PDT) Message-Id: <199810241922.MAA11687@gull.prod.itd.earthlink.net> To: Subject: FreeWWWeb Internet Access - No Monthly Payments EV Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wouldn't you rather pay $126 ONCE than $20 a month (or ANY monthly fee for that matter) for ever? With FreeWWWeb there will never be any monthly payments again.... That's right NO MONTHLY PAYMENTS EVER!!! Here's What You Get With FreeWWWeb: -Free Lifetime Internet Access -Free e-mail account (yourchoice@freewwweb.com) -Free Netscape Navigator 3.2 on CD -Easy to install software -AOL Compatible (Only $9.95/month with no busy signals!) -Free telephone techinical support/customer service For more information and to sign up with FreeWWWeb, go to our website at: http://freewwweb-access.com/freeweb.cgi?id=1389-45 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message