Thank you for pointing out the code.
> It checks to see if config exists, and does nothing if it does. Maybe
> you need to get rid of config, then run YAIM again. That should make it
> work, as config would be remade?
Unsatisfactory IMHO. Bristol's going to move the MON & BDII services from
one server to a new server in future & it was assume running a yaim function
to configure the service on various nodes would change from old to new server.
(NB I've never moved a service like BDII or MON, if anyone's got a good HowTo
pointers are *most* welcome)
It seems clumsy/inelegant to (for instance) have to hunt throughout /opt for
embeddings of the old server name to change to new. ick.
If the yaim functions check for existence of files (that it would create)
without confirming the contents are correct, that seems a bit of a bug.
Maybe yaim wouldn't necessarily rewrite the file (think maui.cfg!) but could
output that the file already exists with contents that don't match what
the site-info.def variables say it should be (like $CE_HOST).
Just my 2p.
And thanks *immensely* to everyone who helped out with advice about
users.conf/groups.conf & QUEUE_ENABLE stuff.
I'm very grateful to you all. Next GridPP I'll be buying brews for yous!
|