On Thu, 9 Jan 2003, Steve Traylen wrote:
> # gpp-fetch-edg-release -r v1_4_2 -o /tmp
FWIW, "gpp-fetch-edg-release" -> "gpp-fetch-edg-release.sh", I think.
> # cp /tmp/edg-release/source/* /var/obj/conf/profile/source/.
Obviously being careful not to overwrite your own site-cfg.h (which I
almost did).
> #define SITE_EDG_VERSION v1_4_2
> in /var/obj/conf/profile/source/site-cfg.h
On a related note, when does SITE_INSTALLATION_DATE_ get modified? Only
the first time the testbed is ever installed, or on each "significant"
upgrade? i.e. should I update it now, since I'm doing the v1_4_0 ->
v1_4_2 upgrade?
> Recompile your profiles and reboot the machines.
Is there an alternative to rebooting them? If the machines are "in use"
then presumably bringing them down with a reboot will force the issue of
stopping all processes and avoid having any software changing under the
feet of active processes, however in the longer term when clusters will,
presumably, be active 24/7 how will this sort of upgrade take place?
Cheers,
Ian.
--
Ian Stokes-Rees [log in to unmask]
Particle Physics, Oxford http://www-pnp.physics.ox.ac.uk/~stokes
|