From owner-freebsd-hackers  Sun Apr 27 19:14:10 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA13190
          for hackers-outgoing; Sun, 27 Apr 1997 19:14:10 -0700 (PDT)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA13185
          for <freebsd-hackers@FreeBSD.ORG>; Sun, 27 Apr 1997 19:14:06 -0700 (PDT)
Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id MAA14114; Mon, 28 Apr 1997 12:13:57 +1000 (EST)
Date: Mon, 28 Apr 1997 12:13:56 +1000 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Best way to hook into user logins / logouts ?
In-Reply-To: <199704280137.LAA13348@genesis.atrad.adelaide.edu.au>
Message-ID: <Pine.BSF.3.91.970428121211.10264s-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Mon, 28 Apr 1997, Michael Smith wrote:

> > So right now the only viable way is to watch wtmp/utmp.
> 
> 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.

Something like the routing socket, which libutil/log{in,out}() can write 
to, and other processes listen for changes....?

Danny