[ET Trac] [Einstein Toolkit] #619: launching jobs with simfactory without necessarily syncing the sources
Einstein Toolkit
trac-noreply at einsteintoolkit.org
Thu Oct 13 20:55:03 CDT 2011
#619: launching jobs with simfactory without necessarily syncing the sources
--------------------------+-------------------------------------------------
Reporter: anonymous | Owner: eschnett
Type: enhancement | Status: new
Priority: optional | Milestone:
Component: SimFactory | Version:
Resolution: | Keywords: simfactory remote directory
--------------------------+-------------------------------------------------
Comment (by knarf):
You are right Ian, but if I understand correctly, Luca tries to submit
from a remote machine - his laptop. I might have created that confusion in
the first place, thinking along the same lines as you now Ian. Simfactory
does figure out the right directory when invoked from within a Cactus
tree, at least I am pretty sure it does. From remote however, it does not
have a good way to determine where Cactus is actually installed - and it
might even be installed in multiple places.
In this case the only option is to tell simfactory. One possibility is of
course to change the machine entry directly, but the better, and intended
option is to change the corresponding entry in the configuration file
defs.local.ini. This file isn't stored in the svn repository and cannot
come into conflict when updating simfactory itself, and it is much harder
to accidentally commit such user-specific entries.
This only leaves the question open what the simfactory default should be.
At the moment it is probably just the preference of the original author of
the configuration, and it is up to the bulk of the users of that
particular machine to agree on something and request it to be the default.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/619#comment:4>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
More information about the Trac
mailing list