From owner-freebsd-questions@FreeBSD.ORG Fri Mar 24 14:17:36 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 2956616A41F for ; Fri, 24 Mar 2006 14:17:36 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail4.sea5.speakeasy.net (mail4.sea5.speakeasy.net [69.17.117.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4CF943D55 for ; Fri, 24 Mar 2006 14:17:34 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 9708 invoked from network); 24 Mar 2006 14:17:34 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail4.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 24 Mar 2006 14:17:34 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 6101528425; Fri, 24 Mar 2006 09:17:33 -0500 (EST) Sender: lowell@be-well.ilk.org To: troy@twisted.net References: <20060323131144.GA99173@twisted.net> From: Lowell Gilbert Date: 24 Mar 2006 09:17:33 -0500 In-Reply-To: <20060323131144.GA99173@twisted.net> Message-ID: <44irq4exky.fsf@be-well.ilk.org> Lines: 11 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: undefined variable error on startup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Mar 2006 14:17:36 -0000 Troy writes: > I'm trying to track down an error I see upon booting. > > Mar 18 14:49:01 server term: Undefined variable > > I'm not sure what file and what term variable is being set so I can > comment it out. Any help on how I can track this down I'd appreciate. Looking at what is just before and just after that message will probably give you a reasonably close idea of where the problem is.