Dan Melomedman writes:
> Sam Varshavchik writes:
>
>> Since HTTP is a stateless protocol, you have no way of knowing if someone
>> whose last HTTP request came in fifteen minutes ago is still reading his
>> mail, or if he is no longer online.
>
> It should be possible to keep a number of total authentication requests in
> authdaemond process per day for instance, no? Also failed requests, so on.
> This could be neat, but like who cares?
But this is not going to tell you how many simultaneous users you had. If
you had a 1000 authentication requests, they could've occured evenly
throughout the day, or all at once.
You could assume an average length of a login session, and end up with a
ballpark estimate of the maximum # of concurrent users, but that's about it.
--
Sam
