Opened 17 years ago
Last modified 17 years ago
#5 new defect
Pseudo-logins are per-user, rather than per-login
| Reported by: | kchen@MIT.EDU | Owned by: | nelhage@MIT.EDU |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | zephyr | Keywords: | |
| Cc: |
Description
Pseudo-logins and pseudo-logouts only look at a user's first location. If a user is logged into multiple locations and logs out of the location listed first in zlocate output, barnowl displays a pseudo-login of the location that is now first, rather than a pseudo-logout for the first location. Only when a user logs out of all locations does barnowl issue a pseudo-logout.
Change History (3)
comment:1 Changed 17 years ago by kchen@MIT.EDU
- Component changed from internals to zephyr
comment:2 Changed 17 years ago by kchen@MIT.EDU
- Summary changed from Pseudo-logins only look at first zlocate entry to Pseudo-logins are per-user, rather than per-login
comment:3 Changed 17 years ago by kchen@MIT.EDU
Hmm. This still isn't quite accurate:
-> LOGIN for kchen (vinegar-pot.mit.edu) 12:45
LOGOUT for kchen (gaston.mit.edu pts/4) 12:46 LOGIN for kchen (gaston.mit.edu pts/4) 12:46 LOGIN for kchen (grobda.mit.edu mrow?) 02:10 LOGOUT for kchen (grobda.mit.edu mrow?) 02:10 LOGIN for kchen (grobda.mit.edu pts/17) 02:10 LOGIN for kchen (gaston.mit.edu mrow?) 11:25 LOGOUT for kchen (gaston.mit.edu mrow?) 11:25 LOGIN for kchen (gaston.mit.edu pts/2) 11:25 LOGOUT for kchen (grobda.mit.edu pts/17) 11:42 LOGIN(PSEUDO) for kchen (gaston.mit.edu) 11:44
The difference in behavior might be related to whether the user announces logins and logouts. In my case, I do, while the other users I saw the other pseudologin behavior with do not.
It seems that at some point, the behavior of pseudo-logins changed, such that they are now per-user, rather than looking at the first zlocate entry. To be consistent with regular zephyr logins, however, and to provide more information, they should be per-login.