Date: Mon, 13 Jan 1997 08:57:38 +0100 (MET) From: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-current@freefall.freebsd.org Subject: Re: a last word on last Message-ID: <199701130757.IAA05591@gilberto.physik.rwth-aachen.de> In-Reply-To: <Mutt.19970112215435.j@uriah.heep.sax.de> from J Wunsch at "Jan 12, 97 09:54:35 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> As Christoph Kukulies wrote: > > > Well, I zeroed wtmp/utmp several times in the past and the problem > > came back. This may because of the various changes to the wtmp/utmp thing. > > There has only been a single change yet. > > You can also use src/tools/3.0-upgrade/cvs-wtmp. I did that a couple of times and either cvs-wtmp barfed at some entries or it didn't work for some other reasons. > > > Anyway, yes, it looks ok now after deleting/touching wtmp/utmp again. > > Though some entries will have to accumulate still to get a better picture. > > It looks that something is still writing in the wrong format, probably > third-party software. Maybe Xaccel? But why do we pile up obstacles for running third party software? I don't expect that Xinside care for holding ready versions for pre and post 2.2 FreeBSD. I know that the wtmp/utmp issues have been discussed widely but a clearing word on this issue would really be helpful. What is the idea to cope with this problem? > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701130757.IAA05591>