#1772: Simfactory: potentially serious problem with CACHE directory in the simulations directory -------------------------+-------------------------------------------------- Reporter: bmundim | Owner: Type: defect | Status: new Priority: critical | Milestone: ET_2015_05 Component: SimFactory | Version: development version Resolution: | Keywords: CACHE -------------------------+--------------------------------------------------
Comment (by bmundim):
Hi Ian:
Replying to [comment:2 hinder]:
Another problem is that during the transition from simfactory 1 to
simfactory 2, a feature was lost. SimFactory 1 used to additionally make a hardlink of the executable in each restart directory. This made it possible to replace the executable at the top-level of the simulation while it was running, so that the next restart would get the new executable (you have to be careful to delete the original hardlink first, because cp by default will copy the new data into the old file, which affects all hard links). If you do that now, the simulation will crash with a "bus error" (at least, that's what happened to me), because each restart executes the top-level executable.
I think if you have a copy of the executable at simulations/SIMFACTORY/exe you could just change for another one and restart the simulation without a problem. I did this for a simulation someone else run and I had to continue. We do need to be extremely careful on this new executable since it could easily segfault if we don't use a very similar Cactus source from the previous simulation.