Re^2: RPM Download Request

Well, first of all, I would ask you: Is this really something you want to do ?
Micro$oft installs automagically software packages when they get available and that is the reason why sometimes you have to wait until you can close your notbook and put it into its bag.
You should understand what your SW should do, if somthings go wrong ( file system full, Internet connection breaks down, conflicting versions, ... ). In my years as sysadmin I was never happy with unattended package installations. Said that, in Unix you have a powerful shell, which can do a lot of things included running commands. I would use the tool expect, which is written exactly for your purpose. I.E. executing commands and react on the output.
Anyway, have fun ....

Comment on Re^2: RPM Download Request

Replies are listed 'Best First'.
Re^3: RPM Download Request by 1s44c (Scribe) on Jul 07, 2014 at 20:26 UTC
Attended package installations don't scale further than a handful of systems. Unattended package installations scale to millions of systems. I've installed packages on many thousands of HP-UX and Linux servers and cluster nodes as part of my day job for many years using homebrew scripts, HP's software distributor, cfengine, and more recently puppet. Normally I only get something like a 0.05% to 0.5% failure rate and that's normally due to either hardware failure or a network issue that's gone away next run. If you can't trust your systems to install a package cleanly your systems are too dirty. You should know what versions of things they are running and you should have the filesystems split so users can't fill system disks.	[reply]

Replies are listed 'Best First'.

Re^3: RPM Download Request
by 1s44c (Scribe) on Jul 07, 2014 at 20:26 UTC

Attended package installations don't scale further than a handful of systems. Unattended package installations scale to millions of systems.

I've installed packages on many thousands of HP-UX and Linux servers and cluster nodes as part of my day job for many years using homebrew scripts, HP's software distributor, cfengine, and more recently puppet. Normally I only get something like a 0.05% to 0.5% failure rate and that's normally due to either hardware failure or a network issue that's gone away next run. If you can't trust your systems to install a package cleanly your systems are too dirty. You should know what versions of things they are running and you should have the filesystems split so users can't fill system disks.

[reply]