I've been mirroring binary packages for the x86 architecture for several months now (woody, sarge and sid). The mirror's size hovered around 15 Gb for a while, but in the last two weeks appears to have suddenly increased to almost 21.5 Gb.
Is there really that much material, or do I need to investigate my rsync scripts?
Kevin
du -hs debian 15G debian
One of us does unless another 6.5 GB has been added in the last two days. I use to be closer to 10GB, and as of last Saturday morning I am up to 15GB. (I mirror once a week) I tried the example config in anonftpsync (-> rsync ) and it got all kinds of archs and stuff I didn't want because there were ones not listed in the example.
Going with a "only grab what I know I want and exclude the rest" theme, I came up with the following:
EXCLUDE="
--include Contents-i386.gz --exclude Contents-*.gz \
--include binary-i386/ --exclude binary-*/ \
--include disks-i386/ --exclude disks-*/ \
--include *_i386.deb --include *_all.deb --exclude *_*.deb \
--include *_i386.udeb --include *_all.udeb --exclude *_*.udeb \
--include *_i386.changes --include *_all.changes --exclude *.changes \
--exclude source/ --exclude *.tar.gz \
--exclude *.orig.tar.gz --exclude *.diff.gz --exclude *.dsc \
"
It's been a good mirror for the past couple months, but that's hardly a full test. Anyone else have a better rsync include/exclude rule list for getting just i386 and "all" arch packages and no sources?
What rules are you using Kevin?
I set my mirror up at work in preparation of switching a bunch of systems to Debian, but since then I've used apt-cacher at home and like it. It's not perfect, but I'm not transferring packages that I may never use. I keep thinking I will just turn off the mirroring, but then I think I want to give my rules a little longer to test them.
-- Jacob
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
