From owner-freebsd-questions Wed Oct 22 19:05:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA19704 for questions-outgoing; Wed, 22 Oct 1997 19:05:10 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA19698 for ; Wed, 22 Oct 1997 19:05:08 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.5) with SMTP id TAA01755; Wed, 22 Oct 1997 19:04:55 -0700 (PDT) Date: Wed, 22 Oct 1997 19:04:55 -0700 (PDT) From: Doug White Reply-To: Doug White To: "User SargeFrank A. Gerbode" cc: freebsd-questions@FreeBSD.ORG, phillips@best.com Subject: Re: Error messages running rc.network In-Reply-To: <199710222137.OAA02498@metapsy.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 22 Oct 1997, User SargeFrank A. Gerbode wrote: > writing to routing socket: File exists > add net default: gateway 206.184.243.169 - file exists > writing to routing socket: Invalid argument > add net: invalid argument > > All of this happens while the machine is running rc.network, the > following section thereof: [...] > I imagine the problem may be in the rc.conf file (I just upgraded > from 2.1.6 to 2.2.0). 2.2.0 didn't have rc.conf. If you upgraded to 2.2.2 or later and didn't remove sysconfig, it's probably getting in the way. Modify rc.conf to reflect sysconfig, move it out of the way, then try it. If /etc/sysconfig still exists, it'll be included, but you'll get a message warning you it's still there and that you should remove it. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major