-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 It's tragedy, man. But 3.1 is too antique against 3.5 to remain unchanged. Also, do not expect good documentation from open source - you can always read sources yourself and know what's changed. Too sad. But this it. WBR, Yuri 28.09.2016 23:48, Daniel Sutcliffe пишет: > I have been using squid 3.1 on EL6 for a long time and recently made > the upgrade to 3.5 - all seems to be working as expected functionality > wise, but I'm noticing a difference in the log file content which is > not helping me doing a bit of peer debugging... > > In 3.1 the access.log used to contain a: > *_PARENT/<peername> > What I'm now seeing is: > *_PARENT/<peer-ip> > > Which wouldn't be so bad if all my <peer-ip> are the same, 127.0.0.1 > as they are all SSH tunnels. > > Otherwise the cache_peer name= directive seems to be doing its job as > far as ACLs are concerned. > > Maybe this is now the expected behavior but I can't seem to find it > documented anywhere - it would be nice if the old log behavior could > be turned back on or I could have it confirmed that what I am seeing > is just the way it is now. > > Cheers > /dan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX7ARNAAoJENNXIZxhPexG2isIALrnOT/TVMd5Nhchf18HFs6b zGoI3KjFD3hpIDrUAFhzFss5WhLc0f/rFwdkEQBpwTjJm8t3jHawoMxo3yDeHqzm 4O9qknEtq1sObI4nCuI9SxK0gXkIqynUKW1fOEWVHGD990H0aw7KiZ5p9T2Ro61q upXOYP0aYiiaTT9bJTxl5l/gzNrU5yGi/NClpV1UbFt/O4MTTrRemZd8NmeP8J2u 6uqRarDaLEv62SDOdbc8xXEw5n+GLkUEVX12I9/oXvwrwrFGfQhPaSCqgsdvK/rW cycS672NlRu/yTkqdsnPQ/nWtG744lM/OnMwy2I36i/qBAv7q9HBPc0nRpLoZMw= =lKgO -----END PGP SIGNATURE-----
Attachment:
0x613DEC46.asc
Description: application/pgp-keys
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
