Date: Fri, 28 Jun 2002 16:17:30 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.ORG> To: Peter Wemm <peter@wemm.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Mike Barcroft <mike@FreeBSD.ORG>, Robert Drehmel <robert@zoot.drehmel.com>, current@FreeBSD.ORG, robert@FreeBSD.ORG Subject: Re: changing 'struct utmp' Message-ID: <Pine.NEB.3.96L.1020628161524.22605F-100000@fledge.watson.org> In-Reply-To: <20020628200729.30D19390F@overcee.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Jun 2002, Peter Wemm wrote: > > Please, if you're going to do it, do it right. > > Yep. Also: > - make a proper API to deal with it, otherwise things like xterm will trash > the utmp file all over again without a 'final solution'. > - make sure we can extend it in the future without having to do this all over > again. > - I'd quite like a variable sized .db file with a 'standard' getutent() style > interface to it. > - wtmp probably shouldn't be a .db file, but then again, it probably can. At one point, I hacked up a FreeBSD kernel to store utmp in kernel, since I needed fine-grained access control on utmp, and wanted to reduce the need for file-backed databases. I've long since lost the patches, but it actually worked fairly well -- I had to add a few more calls similar to "setlogin"/"getlogin", but adopted the same basic model: tie the information to the session. I kept wtmp in userland, however. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1020628161524.22605F-100000>