From owner-freebsd-arch Wed Nov 7 13:29:36 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4A17B37B41B; Wed, 7 Nov 2001 13:29:32 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fA7LSbP36295; Wed, 7 Nov 2001 22:28:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: arch@freebsd.org Subject: Re: /etc/ttys, /var/run/utmp, ttyslot(3) and {get|put}utx* API In-Reply-To: Your message of "Wed, 07 Nov 2001 07:58:30 EST." Date: Wed, 07 Nov 2001 22:28:36 +0100 Message-ID: <36293.1005168516@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: >> I guess the correct solution is to implement the Single Unix >> "{get|put}utx" API backed by a db(3) file. >> >> http://www.opengroup.org/onlinepubs/007908799/xsh/endutxent.html >> >> Any comments ? > >"Yet another thread-unsafe API for managing databases"? Interesting point, I didn't think of that. On the other hand, I don't see much point in multiple threads competing to fiddle this info since they will all have the same session... Anyhow, I'm mightily leaning towards the idea that /var/run/utmp should die and be moved into the session in the kernel, apart from all the obvious things, this would make some interesting information available in kernel dumps. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message