For a proxy serving 300 users - doesn't seem extreme.

2010/10/01 11:08:48| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 11:11:09| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 11:12:27| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 11:14:14| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 11:16:15| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 11:35:52| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 13:37:26| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 13:38:12| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 13:38:21| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 13:38:33| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 13:39:10| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 14:22:08| AuthNTLMUserRequest::authenticate: need to ask helper
2010/10/01 14:24:16| AuthNTLMUserRequest::authenticate: need to ask helper




Out of interest is it possible to see the total amount of connecting IPs
(or users..) for one day; IPs being unique. So if, at the end of today, I
wanted to say 'today there were 60 unique IPs' that used the proxy.. Or is
that more a job for Calamaris or other reporter..?

Nick
Squid3.20STABLE, RHEL5.3x86


On 01/10/2010 13:10, "Amos Jeffries" <squ...@treenet.co.nz> wrote:

>On 01/10/10 23:46, Nick Cairncross wrote:
>> Is the cache.log entry AuthNTLMUserRequest::authenticate: need to ask
>>helper just informational to say a user request has come in and needs to
>>be handed to the ntlm helper?
>>
>> Seems obvious but I just wanted to checkÅ 
>
>Yes.
>
>Is it occuring a lot? I'm not sure it should be at that information
>level. It seems to be one of the regular auth actions instead of an
>important problem.
>
>Amos
>-- 
>Please be using
>   Current Stable Squid 2.7.STABLE9 or 3.1.8
>   Beta testers wanted for 3.2.0.2


The information contained in this e-mail is of a confidential nature and is 
intended only for the addressee.  If you are not the intended addressee, any 
disclosure, copying or distribution by you is prohibited and may be unlawful.  
Disclosure to any party other than the addressee, whether inadvertent or 
otherwise, is not intended to waive privilege or confidentiality.  Internet 
communications are not secure and therefore Conde Nast does not accept legal 
responsibility for the contents of this message.  Any views or opinions 
expressed are those of the author.

The Conde Nast Publications Ltd (No. 226900), Vogue House, Hanover Square, 
London W1S 1JU

Reply via email to