Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: the watch variable
- X-seq: zsh-users 6896
- From: Miek Gieben <miekg@xxxxxxxxx>
- To: zsh users <zsh-users@xxxxxxxxxx>
- Subject: Re: the watch variable
- Date: Mon, 15 Dec 2003 19:35:44 +0100
- In-reply-to: <1031215182445.ZM13075@xxxxxxxxxxxxxxxxxxxxxxx>
- Mail-followup-to: zsh users <zsh-users@xxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20031214000438.GA3374@xxxxxxxxx> <1031215182445.ZM13075@xxxxxxxxxxxxxxxxxxxxxxx>
[On 15 Dec, @19:24, Bart wrote in "Re: the watch variable ..."]
> On Dec 14, 1:04am, Miek Gieben wrote:
> }
> } WATCHFMT='At %T %n has %a from %M.'
> } watch=( notme )
> }
> } And I notice that the login times are correct, i.e. it is the time
> } that the person actually logged in. But the log off times are wrong.
> } I'm seeing the current time in stead of the actual time someone logged
> } off.
> }
> } Is this a bug?
>
> No, though I suppose you could call it a misfeature.
>
> Zsh only examines the most recent 50 records when determining login/out
> times, because searching the entire wtmp file would take far too long.
> So if there's a lot of activity on the system, the record for the person
> in question may have been pushed beyond 50-record region, and zsh falls
> back to the current time.
>
> If that doesn't seem to explain what you're seeing, let zsh-workers know.
yes, that explains it. Although I have never seen it when people are logging
in,
thanks,
grtz
Miek
--
fingerprint = E1EB 29B8 8FA2 2923 62B8 0A2B 64B8 F15C 7764 AB4B
http://miek.nl/about.html
Messages sorted by:
Reverse Date,
Date,
Thread,
Author