Date: Thu, 26 Jul 2001 00:38:14 +0200 From: "Jeroen Massar" <jeroen@unfix.org> To: "'Peter C. Lai'" <sirmoo@cowbert.2y.net> Cc: "'Garance A Drosihn'" <drosih@rpi.edu>, "'Matt Dillon'" <dillon@earth.backplane.com>, <arch@FreeBSD.ORG>, "'Garrett Wollman'" <wollman@khavrinen.lcs.mit.edu>, <brian@FreeBSD.ORG> Subject: RE: Changes to utmp, wtmp & lastlog entries Message-ID: <000f01c1155a$7e268c60$420d640a@HELL> In-Reply-To: <20010725222849.17038.qmail@d170h113.resnet.uconn.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter C. Lai [mailto:sirmoo@cowbert.2y.net] wrote: > all true and good, but i think my issue was that suppose a 3rd party > application doesn't log correctly at all (in the case i > mentioned, it could > be the shell's or pam's or sshd's fault (or some combination > thereof) that > it does not regard HUPing a shell as a proper logout.). > Changing the way > utmp/wtmp is recorded isn't going to change the data. > However, i did say i > probably posted to the wrong thread, but it is still related > to the issue of > erroneous data in lastlog. <SNIP> If you want to 'solve' that you will require kernel hooks of some kind which hook into the begin&exit calls of the task/thread/process. This way one can also catch broken/crashed applications. Then again lastlog/who != ps :) Greets, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000f01c1155a$7e268c60$420d640a>