[squid-users] Error compiling digest-auth-helpers of squid-3.0-PRE3-20060122

I tried compiling digest-auth-helpers from squid-3.0-PRE3-20060122 for use with squid-2.5.STABLE12-20060122 on Mac OS X 10.3.9 with gcc version 3.3 20030304 (Apple Computer, Inc. build 1666). Here're the commands I had used successfully before with squid-3.0-PRE(?)-20050309, but failed today

Re: [squid-users] Error compiling digest-auth-helpers of squid-3.0-PRE3-20060122

Hi, At 14.18 22/01/2006, [EMAIL PROTECTED] wrote: I tried compiling digest-auth-helpers from squid-3.0-PRE3-20060122 for use with squid-2.5.STABLE12-20060122 on Mac OS X 10.3.9 with gcc version 3.3 20030304 (Apple Computer, Inc. build 1666). Here're the commands I had used successfully before

[squid-users] Re: Error compiling digest-auth-helpers of squid-3.0-PRE3-20060122

-3.0-PRE3-20060122 ./configure --host=powerpc-apple-bsd --disable-ident-lookups --enable-auth=digest --enable-digest-auth-helpers=password make ... if gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../include -I../lib/cppunit-1.10.0/include -I ../lib/cppunit-1.10.0/include -Werror -Wall

[squid-users] Re: Error compiling digest-auth-helpers of squid-3.0-PRE3-20060122

Hi, At 16.34 22/01/2006, [EMAIL PROTECTED] wrote: if gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../include -I../lib/cppunit-1.10.0/include -I ../lib/cppunit-1.10.0/include -Werror -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wcomments -g -O2

Re: [squid-users] Squid with SquidGuard

Hello Chaps, I'm still struggling (and still failing) to to squidGuard to work with squid. For those of you who have not been following each gripping instalment of this thread here is a quick recap... I can run squid very happily on my FC4 machine. I have tried installing squidGuard by RPM, by

Re: [squid-users] Squid with SquidGuard

Now, after some Googling, I see that this problem (or at least similar problems) can be caused by a firewall on the loopback interface. Do you think this is the cause of my problem? (I posted my Iptables output in an earlier post). However, as a test, I temporarily disabled the

Re: [squid-users] Squid with SquidGuard

Mark Elsen wrote: That may not be enough in a context where the Firewalling software was started and then stopped. Residual rules and or states may still affect the loopback interface. Can you, for instance, 'ping localhost' with success ? Yup... Even with the firewall up and running: [EMAIL

Re: [squid-users] Squid with SquidGuard

I haven't tried restarting yet - but given that ping localhost works with the firewall(s) in place do you still think that this is my problem? It could still be, so the restarting with all Firewalling off should still be tried. I still think that the Permission denied message is caused by

Re: [squid-users] Squid with SquidGuard

Mark Elsen wrote: I haven't tried restarting yet - but given that ping localhost works with the firewall(s) in place do you still think that this is my problem? It could still be, so the restarting with all Firewalling off should still be tried. Well I've just tried it with

Re: [squid-users] Squid with SquidGuard

... Squid is started automatically in runlevel 5. If I start it myself I use the command: /sbin/service squid start (or stop, or restart) as root. Try to start it more natively, what does : root # path_to_squid/squid -NCd 1 gives ? (You are lucky , the snooker is

Re: [squid-users] Squid with SquidGuard

Mark Elsen wrote: ... Squid is started automatically in runlevel 5. If I start it myself I use the command: /sbin/service squid start (or stop, or restart) as root. Try to start it more natively, what does : root # path_to_squid/squid -NCd 1 gives ? Well Now!