- How to setup a multi-server update tree (r/w)
The easiest solution is to share /var/cache/fou4s of the master machine
via nfs (read/write) and mount it at the same position on the clients.
The master machine is the first that runs fou4s --auto at night. The slave
machines run fou4s --auto a little bit later. Fou4s will only download
packages, that are not installed on the master server.
- How to setup a multi-server update tree (r/o)
On installations with only a few different clients (e.g. lots of SuSE 8.2
machines with the same packages installed), you can use fou4s --auto --host x
for one of them, additionally to the normal fou4s --auto call. Repeat the
fou4s --auto --host call for each host with different packages. If there are
too many different hosts, you can also run fou4s --auto --all to download
the packages (maybe several times with different --suseversion) and then
fou4s -e on the slave machines (of course a little bit later). The CacheDir
on the slave machines must be set to a local directory. The RpmPath must
point to the directory mounted from the server.
- Older SuSE versions can't download packages for SuSE 8.1 and later
Unfortunately the patch description file format has changed, and the path
of the package on the update server cannot be determined any more.
To perform downloads, the missing information (arch) is retrieved from
the file /var/adm/YaST/InstSrcManager/IS_CACHE_0x00000001/DATA/descr/
packages.
If you run fou4s on another machine that downloads for several SuSE servers
with --all, copy the given file from an 8.1 machine into the same directory
on the download machine.