On Thursday 13 July 2006 15:37, Marlier, Ian wrote:
I think it sounds like a great idea, personally...
Given the lack of that particular functionality, I think I might try something like this, though...
`cd /srv/www/htdocs; rsync -arv --delete --exclude=*.ppc* rsync://suse.mirrors.tds.net/suse/update; chkconfig apache2 on; /etc/init.d/apache2 start`
And then point at that machine as your update source, from everywhere else. (and if you didn't want to share it out via http, ftp or nfs or....)
It does mean that you need to download everything; but you only have to do it once. And keeping your update tree up-to-date is just a matter of croning the rsync to run once a day or so.
Hmm. I did state that I didn't want to d/l the whole tree. I have done this in the past, but I end up downloading lots of unnecessary packages.
(One note: I do this, because I have 50 or 60 machines to keep up to date, running a bunch of different suse versions. If you're just looking to keep a few, like 3 or 5 or something, updated, then you probably want to use the public update sites per usual -- rsync can be a heavy protocol, and using it unnecessarily is generally considered to be a Bad Thing.)
Yes, I agree that for medium - large sites, this makes sense. The savings of multiple access outweigh the overhead of d/l'ing the whole tree. For small sites though, I don't want to waste resource d/l'ing packages 3+ times. I think you might find that the 3-5 machine sites outweigh the 50+ machine sites. As I mention in another post in this thread, I've found a package which seems to address a lot of this. It's not complete from my initial investigation, but I could possibly whip it into shape and use that. Something like this would save significant bandwidth on the servers. -- Steve Boddy -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com