From owner-freebsd-questions Sat Feb 9 6:43:55 2002 Delivered-To: freebsd-questions@freebsd.org Received: from sumter.awod.com (sumter.awod.com [208.140.99.1]) by hub.freebsd.org (Postfix) with ESMTP id CB82E37B404 for ; Sat, 9 Feb 2002 06:43:49 -0800 (PST) Received: from teddy.fas.com (pcp01008475pcs.mplsnt01.sc.comcast.net [68.58.200.215]) by sumter.awod.com (8.8.7/8.12.2) with ESMTP id JAA77804; Sat, 9 Feb 2002 09:43:45 -0500 (EST) (envelope-from stanb@awod.com) Received: from stan by teddy.fas.com with local (Exim 3.33 #1 (Debian)) id 16ZYjZ-0008QC-00; Sat, 09 Feb 2002 09:44:09 -0500 Date: Sat, 9 Feb 2002 09:44:09 -0500 From: stan To: Beech Rintoul Cc: Free BSD Questions list Subject: Re: cvsup, rebuild tonite, now /kernel connection attempt t0 ----- fills screen Message-ID: <20020209144409.GA32331@teddy.fas.com> Mail-Followup-To: Beech Rintoul , Free BSD Questions list References: <20020209015522.GA20688@teddy.fas.com> <20020209020554.C216060@nebula.anchoragerescue.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020209020554.C216060@nebula.anchoragerescue.org> User-Agent: Mutt/1.3.27i X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.17 X-Uptime: 09:39:45 up 5 days, 15:15, 1 user, load average: 0.00, 0.00, 0.00 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 08, 2002 at 05:05:54PM -0900, Beech Rintoul wrote: > On Friday 08 February 2002 04:55 pm, stan wrote: > > I just cvsuped, and rebuilt everything. Then I ran mergemaset. > > > > Now the console is continously full of meesages like: > > > > /kernel Conetction attempt to xxx.xx.xx.xx from yy.yy.yy.yy > > > > I'm not runing ipfw, or anything like that, and all of the addresses > > are on the local network. > > > > What have I broken? > > Sounds like you have log_in_vain enabled. Check to make sure > /etc/defaults/rc.conf has the line log_in_vain="0" . Also check /etc/rc.conf > for a log_in_vain="1" if you find it comment it out. > Thanks for pointing me in the direction of the problem. Turns out the new /etc/defaults/rc.conf, and /etc/rc.network don't play nice with each other. From /etc/defaults.conf log_in_vain="0" # >=1 to log connects to ports w/o listeners. And from /etc/rc.network case ${log_in_vain} in [Nn][Oo] | '') ;; *) As you cna see, this results in this feature being enabled, if you don't have any reference to int in /etc/rc.conf Thanks again for the pointer. -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message