An easier sure fire method is to mirror the updates directory via a script
that's run by CRON. I use 'rsync'. The flags mean a=achive retain permissions
and datestamp. v=verbose, --delete-after=remove deleted files and
--partial=resume from last attempt.
Set this to run from CRON at whatever time of the day you wish. You could set
a lock file and check for it prior to running rsync and remove it once rsync
has finished so that two instances of rsync wont be run at the same time.
---------------------------------
#! /bin/sh
rsync -av --delete-after --partial ftp.sunet.se::Mandrake/updates/7.1/RPMS/ \
/mnt/hd/updates/ | sed -n '/MOTD:/!p/'
---------------------------------
Sed strips the "message of the day" remarks from the output.
The following e-mail is sent to root.
---------------------------------
receiving file list ... done
./
kdenetwork-1.1.2-19mdk.i586.rpm
./
wrote 107 bytes read 2744269 bytes 3320.48 bytes/sec
total size is 161931337 speedup is 59.00
---------------------------------
You then either fire up the newer versions of MandrakeUpdate and set the local
directory to "/mnt/hd/updates/" or whatever you've called it and proceed as
normal
OR
if you don't like X, then a simple "rpm -Fvh newerversionof file" from the
command line.
On Sat, 30 Sep 2000, you wrote:
>
> On Sat Sep 30, 2000 at 03:53:54AM +0200, Henrik Edlund wrote:
>
> > > > Is there any non-X version of MandrakeUpdate?
> > >
> > > No. But you can do a mirror of an updates directory for your version
> > > and then use rpm -Fvh yourself if you need to do such updates. The
> > > only problem is you will have to keep an eye on things (either by
> > > subscribing to announce and security-announce) to see when there are
> > > new updates to install.
> >
> > Problem is that information is mailed out hours or even days after the new
> > rpm is released.
>
> Yes and no. I have a bit of a problem here that I'm sure you can
> appreciate.
>
> If I send the email the minute I upload the fix, no one will get the
> update for an hour (or more) depending on which mirror they choose.
> This means people are upset because the updates that have been
> announced are not available.
>
> So we had to delay the announcement by an hour or two (usually not
> more than this, and certainly not days... please tell me what update
> was announced days after it was released... I'll wager you can't).
> The delay is that so when people are alerted that the update has been
> made, most mirrors should have it available.
>
> --
> [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
> // Danen Consulting Services www.danen.net, www.freezer-burn.org
> // MandrakeSoft, Inc. www.linux-mandrake.com
> 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD
>
> Current Linux uptime: 9 hours 34 minutes.
>
>
----------------------------------------
Content-Type: text/plain; name="message.footer"
Content-Transfer-Encoding: 8bit
Content-Description:
----------------------------------------
--
CYA,
Muzza.
Mandrake Linux 7.1
Current Linux uptime: 7 days 22 hours 47 minutes.
Keep in touch with http://mandrakeforum.com:
Subscribe the "[EMAIL PROTECTED]" mailing list.
