[4970] in testers
Re: utmp, the file that wouldn't go away
daemon@ATHENA.MIT.EDU (John Hawkinson)
Tue Jul 10 09:21:41 2001
Date: Tue, 10 Jul 2001 09:21:36 -0400
From: John Hawkinson <jhawk@MIT.EDU>
To: Garry Zacheiss <zacheiss@MIT.EDU>
Cc: testers@MIT.EDU
Message-ID: <20010710092136.W6091@multics.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200107100535.BAA23398@riff-raff.mit.edu>; from zacheiss@MIT.EDU on Tue, Jul 10, 2001 at 01:35:52AM -0400
Garry Zacheiss <zacheiss@MIT.EDU> wrote on Tue, 10 Jul 2001
at 01:35:52 -0400 in <200107100535.BAA23398@riff-raff.mit.edu>:
> I'm not sure why this is happen, but I'll reiterate the feeling that
> we should just nuke utmp and wtmp at boot time
Surely you don't mean wtmp (and wtmpx)? They are supposed to persist.
> and maybe reactivate time.
reactivate seems like a bad idea to me -- we already know that sometimes
reactivate runs when there are people logged into the machine, and having
utmp thus even more screwed up (i.e. inaccurate) seems like a poor plan.
--jhawk
