From owner-freebsd-questions@FreeBSD.ORG Tue Jul 13 00:22:05 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 747DE16A4CE for ; Tue, 13 Jul 2004 00:22:05 +0000 (GMT) Received: from xraided.net (xraided.net [66.88.26.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 587F843D1D for ; Tue, 13 Jul 2004 00:22:05 +0000 (GMT) (envelope-from kyle@xraided.net) Received: from [168.103.174.29] (account kyle HELO kyle) by xraided.net (CommuniGate Pro SMTP 4.1.8) with ESMTP id 1812461 for freebsd-questions@freebsd.org; Mon, 12 Jul 2004 17:22:04 -0700 From: "Kyle Mott" To: Date: Mon, 12 Jul 2004 17:22:03 -0700 Message-ID: <002001c4686f$6c139de0$150ba8c0@kyle> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <20040712234028.GC14633@hardesty.saintaardvarkthecarpeted.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal Subject: RE: Rebuilding wtmp 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: Tue, 13 Jul 2004 00:22:05 -0000 Nevermind, I figured it out. I needed to rebuild ssh. Thanks everyone. -Kyle Mott > -----Original Message----- > From: aardvark [mailto:aardvark@saintaardvarkthecarpeted.com] > Sent: Monday, July 12, 2004 4:40 PM > To: Kyle Mott > Cc: freebsd-questions@freebsd.org > Subject: Re: Rebuilding wtmp > > Kyle Mott disturbed my sleep to write: > > I read a few manpages and did some google'ing, and couldn't find much of > > anything about rebuilding wtmp. I tried just moving wtmp to wtmp.old and > > then doing 'touch wtmp', then logging out and back in, but it still > > reads 31Dec69. Is there some way to fix this? Thanks all. > > It's possible that there's some process holding open wtmp. (You could > check this by adding lsof ("list open files") from ports -- *very* handy > to have around on general principle). If this is the case, probably > the easiest way to fix things would be to rename the file, touch wtmp, > then reboot. > > Interestingly enough, a Google for "wtmp freebsd" turned up this message > from the FreeBSD-Security list: > > http://archives.neohapsis.com/archives/freebsd/2001-07/0055.html > > which suggests "cp /dev/null /var/log/wtmp" to fix things -- at least on > Solaris. > > I am now blessing your keyboard... > > -- > Saint Aardvark the Carpeted > aardvark@saintaardvarkthecarpeted.com > Because the plural of Anecdote is Myth.