Date: Thu, 14 Jan 2010 22:07:29 +0100 From: Ed Schouten <ed@80386.nl> To: Andrzej Tobola <ato@iem.pw.edu.pl> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: utmp/utmpx conversion tool Message-ID: <20100114210729.GN64905@hoeg.nl> In-Reply-To: <20100113225057.GA55325@amp2.iem.pw.edu.pl> References: <20100113194254.GR64905@hoeg.nl> <20100113220010.GC32376@volt.iem.pw.edu.pl> <20100113220238.GV64905@hoeg.nl> <20100113225057.GA55325@amp2.iem.pw.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
--ulYX2yhpjtvapoxU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Andrzej, I'm sending this back to the lists, because I think it is an interesting question. * Andrzej Tobola <ato@iem.pw.edu.pl> wrote: > If I need to preserve datbases - do You have any tool to convert > /var/run/utmp, /var/log/lastlog and /var/log/wtmp to the new format ? I see little use in converting utmp and lastlog to the new format. The utmp file normally shouldn't survive a reboot, while the data provided by lastlog is just `value added'. I can imagine people do want to be able to convert their wtmp files. This is why I just committed a tool called wtmpcvt(1) (also mentioned in UPDATING now). This tool allows you to convert the log files to the new format and view them using last(1) and ac(8). There is no procedure to do this automatically. I also don't want to do this, because if things go wrong, I don't want to be responsible for corrupting everyone's log files. --=20 Ed Schouten <ed@80386.nl> WWW: http://80386.nl/ --ulYX2yhpjtvapoxU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAktPh5EACgkQ52SDGA2eCwU8ywCfQXl3JLMd1LCQzJoQdELzUhcK J+QAnAr1hPdvjW3VvjjMBidEt35851GW =vTMq -----END PGP SIGNATURE----- --ulYX2yhpjtvapoxU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100114210729.GN64905>