Hmmm. Well, I can do one of several things to support automated install/uninstall stuff (no uninstall scripts):
1. Use Packman to uninstall/install the rpms on the headnode and compute nodes. I could invoke Packman via a cexec command for example.
2. Use manual rpm commands. I was actually planning on doing it this way, but the Packman API looks very tempting. I'm still stuck with using a cexec command any way you slice it.
3. Use some combination of one and two, Packman on the headnode and raw cexec commands on the compuite nodes.
I don't need the httpd stuff at this point. I had thought that Packman used the update-rpm stuff, but mebbe i'm wiffing fumes?
-- John
On Thu, 17 Feb 2005, Lombard, David N wrote:
For 4.1, I would suggest install/uninstall be driven from the headnode.
Post 4.1, there are existing plans, e.g., oscar-httpd, and existing but untested update-rpms capabilities, to provide for this. I don't know the current state of the oscar-httpd work, and the update-rpms capabilities were unit-tested a year ago (and now likely suffering from bit-rot).
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
