On Wed, 2012-09-05 at 09:59 -0600, Alex Rousskov wrote:
On 09/05/2012 09:27 AM, Alexander Komyagin wrote:
So you think that it's ok for comm_coonect_addr() to return COMM_OK if
it was called before the appropriate select() notification. Am I right?
Hard to say for sure since
I had a *smalll* issue with my storage so I'm forced to start from
almost scratch.
I previously worked on the 3.2.1 latest stable sources and I am
wondering on where to start now?
start on head? stable?
Eliezer
See http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-7.2/1560/
--
Started by upstream project 3.HEAD-amd64-CentOS-5.3 build number 2039
Building remotely on east in workspace
http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-7.2/ws/
Cleaning
See http://build.squid-cache.org/job/3.HEAD-amd64-opensuse/194/changes
Changes:
[Christos Tsantilas] Bug fix: TLS/SSL Options does not apply to the dynamically
generated certificates
The TLS/SSL options configured with http_port configuration parameter does not
used to generate SSL_CTX context
On 09/06/2012 02:35 AM, Alexander Komyagin wrote:
On Wed, 2012-09-05 at 09:59 -0600, Alex Rousskov wrote:
On 09/05/2012 09:27 AM, Alexander Komyagin wrote:
So you think that it's ok for comm_coonect_addr() to return COMM_OK if
it was called before the appropriate select() notification. Am I
On 09/05/2012 06:58 PM, Amos Jeffries wrote:
On 06.09.2012 11:58, Eliezer Croitoru wrote:
We can pause there for the infrastructure to look fine before moving on
to the store details. I've been waiting on assistance from Henrik or
Alex on that for a while. They are the ones who know the
