Steve,

We're also using LDAP for authentication , using the pam_ldap autheticator (using ldap group)
And I never restarted Squid. So it works perfect!




   Bart
Steve Cody wrote:

I have Squid running in a cybercafe environment.  Frequently, new users
will be added, and existing user's accounts will be disabled.  This is
to enable and disable Internet access for people.

I'm currently using access with a password file that gets modified
whenever there is a user change.  The changes don't take effect until I
restart squid, or do a squid -k reconfigure.

Someone else suggested that I use LDAP to avoid this issue, and I'm
looking into that option right now.

Steve


On Sat, 2003-07-19 at 02:30, Peter Koinange wrote:


Something wrong here, why would you really need to ran squid -k so often, I
believe you problem here is administration I find it impossible see why you
are making changes every 2 minutes. Come up with a admin policy on how often
changes are done and whn they should take effect

Peter
----- Original Message -----
From: "Steve Cody" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 19, 2003 7:31 AM
Subject: [squid-users] Running squid -k reconfigure frequently




Hello all,

I would like to know if there is a negative impact on a system, or on


Squid,


if the squid -k reconfigure command is ran at a frequent interval.  For
example, I would like to run it about every 2 minutes to make user changes
take effect rapidly.

Is that going to be a problem? If so, is there a better interval to use,


or


a better way to make user changes take effect? I'm using user


authentication


and the changes I'm talking about are user creation, enabling, disabling,


and


deleting.  The changes don't take effect until the squid -k reconfigure
command is ran.

Thanks in advance!
Steve Cody

--
Open WebMail Project (http://openwebmail.org)












Reply via email to