#include
After a heated private discussion, the main cause of the problem seems
to be a shortcoming in the metadata update concept. But like with all
big trouble there is no single cause but multiple issues appearing
harmless in the beginning.
First, unlike with non-volatile files, apt-cacher-ng
Hi Eduard
> Keith, please set the ExposeOrigin:1 option in acng.conf
That's just been done.
Keith
--
|Keith Edmunds
|Tiger Computing Ltd
|"The Linux Specialists"
|
|Tel: 033 0088 1511
|Web: http://www.tiger-computing.co.uk
|
|Registered in England. Company number: 3389961
|Registered address:
#include
* Philip Hands [Mon, Oct 04 2010, 06:10:58PM]:
> P.S. Keith, looking back through the logs, it's clear that this has
> been going on for at least a month, and probably longer. It's only
> since the server was upgraded recently that it's quick enough for the
> traffic spike to be as sha
Judging from today's logs, it seems I'm still getting loads of what look
to rather pointless connections from the relevant IP address. Using
ngrep, I see Debian Apt-Cacher-NG/0.5.1 as the user agent in the
requests, although I've not bothered to eliminate the posibility that
you have other clients
4 matches
Mail list logo
