Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 9 Feb 2002 16:53:36 -0800
From:      "Crist J. Clark" <cjc@FreeBSD.ORG>
To:        stan <stanb@awod.com>
Cc:        Beech Rintoul <akbeech@anchoragerescue.org>, Free BSD Questions list <freebsd-questions@FreeBSD.ORG>
Subject:   Re: cvsup, rebuild tonite, now /kernel connection attempt t0 ----- fills screen
Message-ID:  <20020209165336.B18239@blossom.cjclark.org>
In-Reply-To: <20020209144409.GA32331@teddy.fas.com>; from stanb@awod.com on Sat, Feb 09, 2002 at 09:44:09AM -0500
References:  <20020209015522.GA20688@teddy.fas.com> <20020209020554.C216060@nebula.anchoragerescue.org> <20020209144409.GA32331@teddy.fas.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 09, 2002 at 09:44:09AM -0500, stan wrote:
> 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.

Your /etc/defaults/rc.conf and /etc/rc.network are out of sync. Either
you got some _really_ weird CVSup (since I made the changes to both
files with a single cvs(1) commit), our you updated one, but not the
other, during a mergemaster(8) phase or when upgrading /etc by hand.
-- 
Crist J. Clark                     |     cjclark@alum.mit.edu
                                   |     cjclark@jhu.edu
http://people.freebsd.org/~cjc/    |     cjc@freebsd.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020209165336.B18239>