13 messages in org.freebsd.freebsd-archRE: Changes to utmp, wtmp & lastlog e...| From | Sent On | Attachments |
|---|---|---|
| Garance A Drosihn | Jul 24, 2001 12:24 pm | |
| Brian Somers | Jul 24, 2001 3:58 pm | |
| Garrett Wollman | Jul 24, 2001 4:06 pm | |
| Brian Somers | Jul 24, 2001 4:18 pm | |
| Matt Dillon | Jul 24, 2001 4:35 pm | |
| Dima Dorfman | Jul 25, 2001 12:53 am | |
| Peter C. Lai | Jul 25, 2001 12:34 pm | |
| Jeroen Massar | Jul 25, 2001 3:14 pm | |
| Peter C. Lai | Jul 25, 2001 3:28 pm | |
| Jeroen Massar | Jul 25, 2001 3:37 pm | |
| Brian Somers | Jul 25, 2001 6:59 pm | |
| Cy Schubert - ITSD Open Systems Group | Jul 26, 2001 11:49 am | |
| Matthew N. Dodd | Jul 30, 2001 9:19 am |
| Subject: | RE: Changes to utmp, wtmp & lastlog entries | |
|---|---|---|
| From: | Jeroen Massar (jer...@unfix.org) | |
| Date: | Jul 25, 2001 3:37:52 pm | |
| List: | org.freebsd.freebsd-arch | |
Peter C. Lai [mailto:sir...@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 majo...@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message