Hi Craig
Thank you very much for the detailed report and analysis. I think you are
probably right about the problem. I had already noticed the bz2 file
verification is too slow (you notice delays even on a fairly fast machine)
and in the medium term I would like to do this verification step after
download instead of before sending to clients. But I don't think this will
be fixed before sarge releases.
Looking at the code, the timeout is set here (in apt_proxy.py):
self.laterID = reactor.callLater(self.factory.timeout, self.timedout)
self.fatcory.timeout corresponds to the timeout setting in apt-proxy.conf. I
hadn't realised this since this value is supposed to be the network timeout
for backends. So you could increase the timeout but I wonder if it might be
better just to disable the checking completely:
--- apt_proxy.py 2005-03-25 09:04:53.000000000 +0000
+++ apt_proxy.py.noverify 2005-04-06 12:42:34.310102336 +0100
@@ -129,9 +129,6 @@
elif re.search(r"\.gz$", self.path):
exe = '/bin/gunzip'
args = (exe, '-t', '-v', self.path)
- elif re.search(r"\.bz2$", self.path):
- exe = '/usr/bin/bunzip2'
- args = (exe, '--test', self.path)
else:
# Unknown file, just check it is not 0 size
try:
That will disable the use of bunzip2 and apt-proxy will only check that the
file is not zero size. Since these files are updated once a day anyway (and
would be replaced if broken) it might be best to do this.
Does that patch work for you?
Chris
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
