From owner-freebsd-hackers Thu Apr 24 11:00:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA20950 for hackers-outgoing; Thu, 24 Apr 1997 11:00:47 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA20942 for ; Thu, 24 Apr 1997 11:00:44 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA26438; Thu, 24 Apr 1997 10:56:06 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd026429; Thu Apr 24 17:56:02 1997 Message-ID: <335F9E9A.41C67EA6@whistle.com> Date: Thu, 24 Apr 1997 10:55:38 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Michael Smith CC: David Nugent , abelits@phobos.illtel.denver.co.us, adrian@staff.psinet.net.au, freebsd-hackers@freebsd.org Subject: Re: Best way to hook into user logins / logouts ? References: <199704241351.XAA27716@genesis.atrad.adelaide.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: > > David Nugent stands accused of saying: > > > Can you suggest a means of starting a session that doesn't involve : > > > > > > getty > > > telnetd > > > rlogind/rshd/sshd/etc. > > > xdm > > > > Personally, I think you're confusing "login" (gaining direct > > access to a system, or opening and entering a door) with > > "authentication" (the locks we put on the doors). > > The definative way would be to allow the kernel to notify a process aupon the creation of new sessions and the closing of the last process in a sesion. I would suggest that the notification go to init, which could do all the appropriate things