On 05/02/2018 03:07 PM, Cody Herzog wrote:
> So, here is my shutdown sequence:
>
> 1.) Modify config file to prevent new client connections and 'reconfigure'.
> 2.) Poll active requests until there are no connections to critical services.
> 3.) Issue the shutdown command with a small value for sh
Thanks again, Amos.
>Then Squids behaviour already matches your requirements. The "or when timeout
>occurs" is shutdown_lifetime and you do not have to do anything.
I'm confused by this. After issuing the first shutdown command, my desired
behavior is for Squid to shut itself down fully as soon
On Wednesday 02 May 2018 09:11 PM, Amos Jeffries wrote:
On 03/05/18 03:01, Amish wrote:
But the code in Format.cc looks complicated then simple one line:
case LFT_LOCAL_LISTENING_IP: {
// avoid logging a dash if we have reliable info
const bool interceptedAt
On 02/05/18 06:05, joseph wrote:
> hi i tried to patch
> http://www.squid-cache.org/Versions/v5/changesets/squid-5-23da195f75b394d00ddac4fa67ce6895d96292d7.patch
>
> file dose not exist src/ssl/stub_libsslutil.cc should i ignore this and
> consider it an extra mistake in that patch or ??
> even i
On 03/05/18 03:01, Amish wrote:
> On Wednesday 02 May 2018 10:05 AM, Amos Jeffries wrote:
>> On 02/05/18 16:20, Amish wrote:
>>> Does request->masterXaction->tcpClient->local hold Squid IP incase of
>>> intercepted traffic too?
>> The listening address (if any) will be in
>> request->masterXaction-
On Wednesday 02 May 2018 10:05 AM, Amos Jeffries wrote:
On 02/05/18 16:20, Amish wrote:
Does request->masterXaction->tcpClient->local hold Squid IP incase of
intercepted traffic too?
The listening address (if any) will be in
request->masterXaction->squidPort->listenConn->local instead. It has n
