From owner-freebsd-questions@FreeBSD.ORG Thu Jun 17 20:28:04 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BCF316A4CF for ; Thu, 17 Jun 2004 20:28:04 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2220B43D31 for ; Thu, 17 Jun 2004 20:28:04 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from working.potentialtech.com (pa-plum1c-102.pit.adelphia.net [24.53.179.102]) by internet.potentialtech.com (Postfix) with ESMTP id 7366569A39; Thu, 17 Jun 2004 16:27:08 -0400 (EDT) Date: Thu, 17 Jun 2004 16:27:07 -0400 From: Bill Moran To: "Matt \"Cyber Dog\" LaPlante" Message-Id: <20040617162707.23ddfe0a.wmoran@potentialtech.com> In-Reply-To: <20040617192140.C6DE169A39@internet.potentialtech.com> References: <20040615145844.03366089.wmoran@potentialtech.com> <20040617192140.C6DE169A39@internet.potentialtech.com> Organization: Potential Technologies X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: Keep log_in_vain Value X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2004 20:28:04 -0000 "Matt \"Cyber Dog\" LaPlante" wrote: > > -----Original Message----- > > From: Bill Moran [mailto:wmoran@potentialtech.com] > > Sent: Tuesday, June 15, 2004 2:59 PM > > To: Matt "Cyber Dog" LaPlante > > Cc: david@davidfuchs.ca; freebsd-questions@freebsd.org > > Subject: Re: Keep log_in_vain Value > > > > "Matt \"Cyber Dog\" LaPlante" wrote: > > > > -----Original Message----- > > > > From: David Fuchs [mailto:david@davidfuchs.ca] > > > > > > > > Matt "Cyber Dog" LaPlante wrote: > > > > > > > > > Ah, grep saves the day again. It was being turned on in rc.network. > > > > > Thanks. > > > > > > > > > > > > > You sure it wasn't being turned on in rc.conf instead? Anything else > > > > would mean that someone was messing with rc.network or > > > > /etc/default/rc.conf, which really should be left alone. > > > > > > I'm positive...there is no log_in_vain entry in rc.conf. It only > > appears in > > > rc.network, where both tcp and udp were set to 1. > > > > That's really strange ... is you rc.network customized? It really > > shouldn't > > be. > > > > The stock one only sets log_in_vain if /etc/rc.conf tells it to. > > > > -- > > Bill Moran > > Potential Technologies > > http://www.potentialtech.com > > Couldn't tell you, I didn't build this system. It got dumped on me when I > took over a sysadmin job. I guess it's just another checkmark on my list of > really strange things that have been done to this network. :) Be warned ... it's likely that either /etc/rc.network, or /etc/defaults/rc.conf have been modified. Neither of these files should be cusomized, and both will be (and should be) replaced the next time you update this machine. Make sure you backup /etc and all subdirectories before you do the next upgrade, in case the machine's behaviour changes enough that you have to search through the old versions to see see what was going on! -- Bill Moran Potential Technologies http://www.potentialtech.com