From owner-freebsd-stable Wed Jun 28 9:41:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from visionaire.ping.de (visionaire.ping.de [195.37.123.61]) by hub.freebsd.org (Postfix) with ESMTP id 9A87E37B934 for ; Wed, 28 Jun 2000 09:41:14 -0700 (PDT) (envelope-from thomas@visionaire.ping.de) Received: from dante.visionaire.net (dante.visionaire.net [192.168.208.42]) by visionaire.ping.de (8.9.3/8.9.3) with ESMTP id OAA24047; Wed, 28 Jun 2000 14:16:03 +0200 (CEST) (envelope-from thomas@dante.visionaire.net) Received: from thomas by dante.visionaire.net with local (Exim 3.12 #1 (Debian)) id 137Gl9-0000Kb-00; Wed, 28 Jun 2000 14:16:03 +0200 Date: Wed, 28 Jun 2000 14:16:03 +0200 To: Gerhard Sittig Cc: US FreeBSD Stable Mailing List Subject: Re: startup issues after mergemaster Message-ID: <20000628141602.A565@dante.visionaire.net> References: <39570DA1.27D98698@gorean.org> <20000626194920.J9883@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i In-Reply-To: <20000626194920.J9883@speedy.gsinet>; from Gerhard.Sittig@gmx.net on Mon, Jun 26, 2000 at 07:49:20PM +0200 From: Thomas Keusch Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 26, 2000 at 07:49:20PM +0200, Gerhard Sittig wrote: > > | > After doing a mergemaster of configuration files in /etc > > | > this morning (2000/06/26 08:00 CEST) the system fails to > > | > read /etc/rc.conf completely (stops after reading the top > > | > 3 lines, which are nic configparams). > > | > > | What clued you in to it stopping at exactly that point? > > > > On line four I have 'portmap_enable="NO"'. This as all the > > following lines are ignored. > > This sounds very much like an unterminated string -- the ticks / > quotes are opened but never closed. This way the assignment > continues till the EOF. And the RHS is somewhat defective. I had the same problem a few weeks ago. It had something to do with the firewall_* settings in /etc/rc.conf . The issue may have been caused by an weird combination of firewall_script pointing to a custom rc.firewall file and firewall_type being undefined or something similiar. I'm sorry I can't be more precise, as I don't have a copy of my old stuff left and have not had the time to figure out the exact reason back then either. So I suggest commenting out firewall_* and reboot, see if it works, and go from there. Check if you are using firewall_* as it is supposed, I found it to be a bit confusing sometimes. Oh, and don't lock yourself out! :-) -- thomas. .powered.by.debian/linux. .served.by.FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message