From owner-freebsd-arch Wed Nov 7 10:17:42 2001 Delivered-To: freebsd-arch@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 987E837B41A; Wed, 7 Nov 2001 10:17:37 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id fA7IHaT22823; Wed, 7 Nov 2001 13:17:36 -0500 (EST) (envelope-from wollman) Date: Wed, 7 Nov 2001 13:17:36 -0500 (EST) From: Garrett Wollman Message-Id: <200111071817.fA7IHaT22823@khavrinen.lcs.mit.edu> To: rwatson@FreeBSD.ORG Subject: Re: /etc/ttys, /var/run/utmp, ttyslot(3) and {get|put}utx* API In-Reply-To: References: <15786.1004869680@critter.freebsd.dk> Organization: MIT Laboratory for Computer Science Cc: arch@FreeBSD.ORG 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In article you write: >On occasion, I've wondered if this information couldn't be stored >in-kernel and managed using calls similar to get/setlogin(). In point of fact, some of it is stored in the kernel and managed using precisely those calls! Every tty being used for a login is the controlling terminal of some process group, which is associated with a particular session. lognames are stored in the session structure. - -GAWollman -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE76XqxI+eG6b7tlG4RAoqdAKCYknx2Y4x7+5/PZP+zuty/FJJxRACgk+RR TZTrFanNvcxfH7lj2y1Alro= =DJMF -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message