Dear Henrik: Thanks for the reply.I tried fixing the uid/gid and the authenticatorprocessed no longer crashed. However, squid never seemed to be using them to do the authentication.The ACL and http_access parts of my configuration file are ported fromthe old config which actually worked. These parts of the config file are largely identical to the defaultone, except for the one ACLof "proxy_auth" and the corresponding http_access entry. The result is that squid never really authenticate a user matching theproxy_auth ACL. If one surfs the web via my cache, he gets an "AccessDenied" error page from squid, and there are no prompt for enteringusername and password before the error page is delivered. I tried thePAM authenticator and the result was similar. I guess I'll have to downgrade to 2.6 and do some comparisons to findout the problem. Regards, Cong. On Sun, May 18, 2008 at 11:06 PM, Henrik Nordstrom<henrik@xxxxxxxxxxxxxxxxxxx> wrote:> On sön, 2008-05-18 at 11:56 +0800, frigoris.ma@xxxxxxxxx wrote:>>> [ omitted: squid initializing ]>> 2008/05/18 03:21:49| helperOpenServers: Starting 5 'squidauth.pl' processes>> 2008/05/18 03:21:49| ipcCreate: /usr/lib/squid/squidauth.pl: (13)>> Permission denied>> Maybe your cache_effective_user setting changed, making the helper now> run under a different userid than before..>> Regards> Henrik>
