From: Chris H. <chr...@gm...> - 2002-05-02 08:02:04
|
On Thu, May 02, 2002 at 10:49:00AM +1000, Roland Gerlach wrote: > Periodically I burn a CD of the .deb files in apt-proxy directory on the > work system and copy the files into the apt-proxy directory at home. > Apt-proxy seams to cope with this and when I upgrade the home systems, it > performs the rsync which sends and receives only a couple of hundred bytes > to confirm that the file is up-to-date. Still much better than performing > an rsync with a previous version. >=20 > Unfortunately, when I upgrade another system at home, apt-proxy performs = the > same rsync over and over again. I'd really like to avoid the additional > traffic - any suggestions? Hmm, that behaviour sounds odd. I can't tell you why it's happening like that. Maybe you can add DEBUG=3Dtrue to /etc/apt-proxy/apt-proxy.conf and send me a copy of /var/log/apt-proxy.log for such a session? Normally, apt-proxy will not try to re-rsync a .deb once it has it in its cache. This is because once a .deb is put in the archive, it is never changed - changes are uploaded with a new filename. Packages and Sources files do get re-updated - if the inode change time is older than BACKEND_FREQ minutes. But that only happens when you run apt-get update, not apt-get install.=20 > Today I discovered apt-proxy-import and will give it a try tonight to see= if > it avoids these extra rsyncs. I don't think it will, because it just copies the file into the correct directory, and renames it if necessary. That is the same as your copy from CD. HTH, Chris --=20 Chris Halls | Frankfurt, Germany Yahoo:hagga12000 ICQ:36940860 MSN:chr...@ni... |