--nivyF5ZmfdQ/+RfC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 18, 2005 at 06:48:29AM -0400, Michael Shalayeff wrote:
| Making, drinking tea and reading an opus magnum from David Lee:
| > On Sat, 16 Apr 2005, Andrew Bartlett wrote:
| > Use of the higher-level subroutines ("pututline()", "login()" etc.), =
where
| > provided by the OS, certainly seems preferable. For one thing, it sh=
ould=20
| > (assuming no bugs!) manage locking, in a consistent fashion, of the=
=20
| > underlying utmp/wtmp database files. (Imagine two or more simultaneo=
us=20
| > connects or disconnects of any entities (ftpd, telnetd, sshd, smbd, .=
...)=20
| > which try to update those database files.)
|=20
| those interfaces do not exist in *bsd.
| login/logout is unusable as well and it is explained
| in the comments in my diff WHY

login(3) and logout(3) certainly exist in NetBSD's libutil, and NetBSD
has had them since inception (March 1993). FreeBSD has them.
OpenBSD should have them as NetBSD had them at the time OpenBSD forked
from NetBSD, unless they've since been removed.

With the addition of utmpx(5) support in NetBSD a couple of years ago,
NetBSD also provides loginx(3), logout(x) and logwtmpx(3) APIs in=20
libutil, as well as the POSIX pututxline(3) (et al) API in libc.

autoconf tests can be used to detect which particular utmp/wtmp/utmpx/wtmpx
APIs are present and working on a given system so that Samba can DTRT.


I hope that helps,
Luke.

--nivyF5ZmfdQ/+RfC
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFCZEfopBhtmn8zJHIRAjSNAJ9lr62E5JuMm+IPuTw6EX/gV/A/2wCgtyld
ijXHUgDZF6/yk3BRPgMX2AU=
=8tGg
-----END PGP SIGNATURE-----

--nivyF5ZmfdQ/+RfC--