| Background job on remote machine: problems with IDL_IDLBridge [message #85609] |
Wed, 21 August 2013 09:23  |
mg.elianto
Messages: 4
Registered: August 2013
|
Junior Member |
|
|
Hi all,
this is Mario Gennaro writing (Space Telescope Science Institute), I am new to the group, I hope I'll find some help for my problem.
I am used to run background IDL jobs on remote machines; this usually works:
ssh -Y2 me@remotemachine
nohup $IDL_DIR/bin/idl < input-commands-list >& output-log-file
then I can ctrl-d and let the process run on the remote machine. eventually I can log back in and see the progress by:
tail -f output-log-file
Fine; however I have problems when the IDL code running requires X windows.
I solve this by writing codes that don't plot anything.
Again, this works BUT here is the big trouble:
one of my codes uses the IDL_IDLBridge, which seems to require a valid X windows to exist, even if the child process doesn't plot anything.
I thought I could solve this by using screen instead of nohup, but it doesn't seem to work.
I tried to ssh into the remote machine, create a screen session, the launch my program within the screen session:
ssh -Y2 me@remotemachine
screen -R "Foo"
screen-Foo-prompt $: $IDL_DIR/bin/idl < input-commands >& output-file
ctrl-a d
I can detach from the screen session, and the code keeps running, but if I disconnect from the remote machine (ctrl-d), I obtain this error (when I look back into the output log file):
X connection to localhost:10.0 broken (explicit kill or server shutdown)
Any clues?
Cheers,
Mario
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
