Date: Mon, 28 Apr 1997 11:07:02 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: davidn@unique.usn.blaze.net.au (David Nugent) Cc: msmith@atrad.adelaide.edu.au, terry@lambert.org, 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 ? Message-ID: <199704280137.LAA13348@genesis.atrad.adelaide.edu.au> In-Reply-To: <199704250344.NAA17710@unique.usn.blaze.net.au> from David Nugent at "Apr 25, 97 01:44:02 pm"
index | next in thread | previous in thread | raw e-mail
David Nugent stands accused of saying: > > Actually, I have to look at xdm shortly. Aparently David did > some basic login class support, but the 3.2 for -current > release appears to be missing a few things, if it is done > at all. If you get a chance, have a look at how the CDE 'dtlogin' thing works. As I read it, it's a PAM consumer in some (Sun, HP, Digital) implementations. It would perhaps be good to be 'similar'. > So right now the only viable way is to watch wtmp/utmp. > This sucks from the pov that some polling is involved, > but even that could be mostly solved when/if poll() is > implemented and when/if it would be possible to block > on mtime change on a file descriptor. That's not really necessary, presuming that the wtmp/utmp changes are being made by things that are under "our" control. The PAM gear has 'at logout' hooks as well. > David (I _really_ need to stop talking about this stuff and do something with it 8( ) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704280137.LAA13348>