Mailinglist Archive: opensuse (2831 mails)

< Previous Next >
RE: [SLE] On-demand caching local mirror?
  • From: "Marlier, Ian" <ian.marlier@xxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 13 Jul 2006 10:37:10 -0400
  • Message-id: <D2575519D6CA2840B6D3E26087EA71B6C8AA@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>

> -----Original Message-----
> From: Stephen Boddy [mailto:stephen.boddy@xxxxxxxxxxxxxx]
> Sent: Wednesday, July 12, 2006 10:21 PM
> To: suse-linux-e@xxxxxxxx
> Subject: [SLE] On-demand caching local mirror?
> I'm wondering if anyone can come up with an answer. I'm after a piece
> software that will "mirror" an ftp directory (as an example) locally,
> will not retrieve the files unless read. I'm sort of thinking of a
> sort
> of local filesystem.
> i.e. The SUSE updates repository.
> 1. Set up a local folder.
> 2. Get the remote file list.
> 3. An app requests a file.
> 4. If in local cache, return file, goto 3
> 5. If not local, and if connection closed, reopen.
> 6. Try to retrieve, then return file, goto 3
> (every so often (on mount, once/day) repeat 2)
> The point being that I have multiple machines I want to update, so I
> want to waste bandwidth by a) downloading the kde updates repeatedly,
or b)
> replicating the whole folder with updates for packages I haven't
> It seems like this would be a sensible addition to SUSE for those of
> with
> multiple machines, (applying to virtual ones too.) I've googled, and
> through lots of pages, but I can't find something that operates like
> The closest I seen so far is fuseftp. The two problems I can see with
> are
> 1. I think the cache expiry time is specified in seconds, and I can't
> if
> there is an indefinate (i.e. passing 0)
> 2. I think it holds the ftp connection open while it is mounted, which
> wouldn't be good for the servers, with people holding connections
> Any suggestions?

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://; 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

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.

(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.)

Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

< Previous Next >
Follow Ups