orun and OmegaApps always use default.cfg

[derek-gerstmann]

When invoked from the command line with a specific config, like so:

./orun -c ../../system/test-multinode.cfg

The launch commands that get generated assume that the default.cfg is going to be used, instead of passing on the user specified display config.

[febret]

I double checked the code and it looks correct (https://github.com/uic-evl/omegalib/blob/master/src/omega/osystem.cpp#L412) but I will try running it on our cluster tomorrow to see if I can reproduce.

You can also try to do

./orun -c ../../system/test-multinode.cfg -L d

and see if in the detailed log the commands in the lines starting with *_[olaunch] *_look correct