Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Thank you in advance for any help you can provide. We are currently using squid 3.0 STABLE 13 and squidGuard 1.3 with NTLM Authentication on a SuSE 10 server. squid has been working beautifully however as the number of users have grown we now have a issue with squid crashing when there are I assume no more available ntlm_auths left. Here is a section of my squid.conf as the whole file is too long to post here:
auth_param ntlm program /usr/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp
auth_param ntlm children 240
# auth_param ntlm max_challenge_reuses 0 #added by Lee Higginbotham
# auth_param ntlm max_challenge_lifetime 2 minutes #added by Lee Higginbotham
external_acl_type nt_group ttl=10 children=25 %LOGIN /usr/local/squid/libexec/wbinfo_group.pl
If you will note two of the commented out lines that have "added by..." I am thinking will help my issue. I also think by changing the half_closed_clients to "off". It currently is commented out:
# TAG: half_closed_clients
# Some clients may shutdown the sending side of their TCP
# connections, while leaving their receiving sides open. Sometimes,
# Squid can not tell the difference between a half-closed and a
# fully-closed TCP connection. By default, half-closed client
# connections are kept open until a read(2) or write(2) on the
# socket returns an error. Change this option to 'off' and Squid
# will immediately close client connections when read(2) returns
# "no more data to read."
# half_closed_clients on
I have two questions:
1. What is the maximum number the auth_param ntlm children can have?
2. Would the max_challenge_reuses, max_challenge_lifetime and half_closed_clients option assist with the possible crashing of squid?
Again, thank you for any assistance.
I've changed the half_closed_clients option to off and it is still crashing. Really, any help at this point would be great!!!
More information...Squid was working very well until we upgraded our AD to Windows 2008. So, it looks like it might be a problem with the authentication with 2008. I'm going to do more research! Thanks to all in advance of any help.
Last edited by lhiggie; 05-20-2009 at 08:40 AM.
Reason: Update to the post