Re: Internal "mirror" for fou4s

On Jan 29, Bernd Felsche <[email protected]> wrote:

> I've finally bitten the bullet and "done it right".
>
> The FAQ page mentions a couple of methods of keeping several hosts
> updated from a common archive.
>
> One option not mentioned is to set up a "mirror" using an httpd.
>
Your apache setup seems to be ok.
>
> On each client, run
> 	fou4s --export client.fou
> and transfer the file to the master server.
Uhhhmm ... no. The import/export feature was thought for completely
offline hosts. You should rather run "fou4s --host client1", which imports
the RPM db of that host via SSH.

> Proceed with updating the master server
> 	fou4s --auto --checkfou4s
No, you must run the --auto together with the --host parameter of the
client. If several clients have nearly the same files, they are only
downloaded once. I'd probably also don't use --auto but fou4s -ued (update
patch descriptions, examine, download) and redirect to /dev/null. The
clients should run fou4s a bit later and will just find the new packages,
send notification mail, etc.
I have yet to think of a mechanism for "publishing" updates, e.g. the
admin tries an update on his test machine and says "ok, I want this on all
others".
I must admit, that I don't use such a setup anywhere, because I've never
had a farm of SuSE machines to handle :(
Only a couple of machines here and there - still handled manually.

Markus
-- 
__________________    /"\
Markus Gaugusch       \ /    ASCII Ribbon Campaign
markus(at)gaugusch.at  X     Against HTML Mail
                      / \
--