-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi gents,
I run subj on testing environment in transparent mode under Solaris 10
and have a bit questions. ;)
1. Squid 3 must absolutely run from root (and drops privilegies to user
squid createrd first) under Solaris 10. It absolutely can't work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is bug 4057.
It is fixed in the latest daily snapshot for 3.4 series. Or the patch
can be downloaded from here:
http://www.squid-cache.org/Versions/v3/3.4/changesets/
Amos
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Hello,
I have a succesful version of squid installed on a CentOS 6.5 box, and
another Centos65 box where it is not working when I type service squid
start Both boxes have the identical squid configuration, and i ensured
that they were both running the same version, 3.4.8
From the cache.log file:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Derek,
To verify that these boxes has the same settings I would start running
the basic_data.sh script at:
http://www1.ngtech.co.il/squid/basic_data.sh
This script will might find the culprit with the issue pretty fast.
I assume you have used
Hello,
Yes it is true I am using the RPM repository to do the install. I have
downloaded your script and I will see if I can find any differences that
may be the culprit. In the meantime I thought I may be on to something -
but I am not sure. Is that error message one that you may get if the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/23/2014 12:26 AM, Derek Cole wrote:
Hello,
Yes it is true I am using the RPM repository to do the install. I
have downloaded your script and I will see if I can find any
differences that may be the culprit. In the meantime I thought I
may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/23/2014 12:49 AM, Derek Cole wrote:
Ok - thanks for saving me from chasing that issue down.
I am not currently using selinux:
Then make sure that selinux is on not on enforced mode and if so the
issue might be because of a missing directory
Sorry, my previous message got sent prematurely.
As I was saying, I am not currently using selinux
SELINUX=disabled
SELINUXTYPE=targeted
is the configuration on both machines. As for the basic permissions issue,
I thought I read somewhere about a missing pid file, but I don't know when
that
Here is the squid configuration file, on both boxes:
visible_hostname BrowserAccess
#acl localnet src 10.1.1.0/24 # RFC1918 possible internal network
#acl localnet src 10.22.0.0/23
acl all src 0.0.0.0/255.255.255.255
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/12/2014 10:35 a.m., Derek Cole wrote:
Hello,
I have a succesful version of squid installed on a CentOS 6.5 box,
and another Centos65 box where it is not working when I type
service squid start Both boxes have the identical squid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK Amos gave you a suggestion which will cover everything but from
reading the squid.conf I would first try to understand:
What do you want squid to do for you?
You need to remove the all acl line and change the http_port from
what it is to the
Here is the output of the squid -k parse command, AFTER making the
changes suggested by Eliezer
2014/12/22 18:34:40| Startup: Initializing Authentication Schemes ...
2014/12/22 18:34:40| Startup: Initialized Authentication Scheme 'basic'
2014/12/22 18:34:40| Startup: Initialized Authentication
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Alex,
I am not sure what you mean by your question.
I am using latest 6.6 as a build node and am trying to use the most
up-to-date CentOS version and libs.
Downsides? If someone has a 6.5 or older 6 branch system without
enough updates to work
13 matches
Mail list logo
