Hey, i also use the mirror script for this. My config file for the update of 6.4 looks like this: package=suseupdate comment=suseupdate site=ftp.suse.com local_dir=/daten/suse/suse64/update/ remote_user=anonymous remote_password=torsten@webit.de remote_dir=/pub/suse/i386/update/6.4/ passive_ftp=true mail_to=torsten@slave.xtremeweb.de If you want to exclude some files or directories, you could do that also. Hope that helps. Greetings Maarten van den Berg schrieb:
On Wednesday 18 April 2001 13:18, RoMaN SoFt / LLFB!! wrote:
Hello.
Let's suppose I want to have a mirror of *all* 6.4 suse updates. I have several SuSE machines and I'm going to set up on each machine an auto-update script which checks for newer packets by ftp'ing to my local mirror.
I've created this script:
LOCAL=/usr/local/ftp/pub/suse/update wget -m -nH --cut-dirs=4 -P ${LOCAL} ftp://ftp.suse.de/pub/suse/i386/update/6.4 wget -m -nH --cut-dirs=4 -P ${LOCAL} ftp://ftp.suse.com/pub/suse/i386/update/6.4
First I download packets from the German site which if I'm not wrong they are the ones with license/exports problem. Second, I download the rest of the packets from "official" site. Can I trust rpm's not being duplicated on both sites? What's the SuSE's policy about this?
Why not first download from the international site, and THEN from .de, thereby avoiding the problem altogether ?
I think I'm right but.. Am I missing some important update packets on another directory? I need to be sure I'm not missing rpm's.
You get what's there, I guess... no more no less
The script is executed regularly by cron (one time per week is sufficient?). Is there any way of removing old packets from my mirror? This would be avoid a situation like this: -r--r--r-- 1 root root 453985 Aug 29 2000 timezone-2.1.3-150.i386.rpm -r--rw-r-- 1 root root 452109 Jan 25 17:07 timezone-2.1.3-155.i386.rpm
Both files are kept in my local mirror. This is unnecessary.
If you use the "mirror" perlscript it will take care of these. For my own setup, I made some shellscripts that symlink all those downloaded files into several new directories according to several criteria. Thus I try to avoid downloading huge fontfiles or other unneeded stuff like X when I only want to upgrade a firewall, etc. You get the idea. Also, those symlinks effectively merge the separate .com and .de trees into one directory my clients can download from. YMMV. Works for me.
Is it safe to delete automatically (I'll write some script lines) the old files? (eg: compare xxx-2.1.3-150.yyy < xxx-2.1.3-155.yyy and remove the first one). Would I break something?
You shouldn't end up with those two files in the first place. Use mirror, (as was said already). I second that.
P.S.: been there done that. I wanted exactly the same as you want.
Maarten
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com