comp.lang.idl-pvwave archive: archive » Re: Problems with long IDL background jobs

Home » Public Forums » archive » Re: Problems with long IDL background jobs

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Problems with long IDL background jobs [message #37008 is a reply to message #37004]

Fri, 07 November 2003 01:52

Nigel Wade
Messages: 286
Registered: March 1998

Senior Member

J.K. wrote:
> I have some processing that takes about 12hrs so
> I'd like to run this in the background. I'm on
> IRIX. It must be something simple that I'm doing
> wrong. After I log out and close my X11 connections,
> I'll get a message in my log file:
>
> XIO: fatal IO error 131 (Connection reset by peer) on X server "xxxxxxxx:0.0"
> after 116 requests (116 known processed) with 0 events remaining.
>
> Am I not redirecting standard out properly?
> Below is what I'm doing. Any help appreciated.

No, that's the X client (IDL) complaing it's lost its connection to the X
server.

>
> idlstartbg.pro startup file, I only set the path, no device commands.
> !PATH=!PATH+":~/idl:~/wave/wvproc:~/wave/fermi98
>
> runidl batch file:
> #!/bin/csh
> setenv IDL_STARTUP idlstartbg.pro
> idl $1 >& log.$1 &
>
> runback.pro
> .run sdsnan
> exit
>
> sdsnan.pro is a main
> filelist = strarr(600)
> openr, unit, "list",/get_lun
> i = -1
> fn = ' '
> while (not eof(unit)) do begin
> i = i + 1
> readf, unit, fn
> filelist(i) = fn
> print, i,filelist(i)
> endwhile
> close, unit
> ; do lots of other stuff with some print statments
> end
>
> How I execute:
> nohup runidl runback >& out &
>
> exit (close X window)
>
>
> Produces:
> out: empty
> log.runback has standard out but also the X11 message and job does not
> complete.
>
> What am I doing wrong?
> If I change all print to printf in sdsnan.pro to write to a file it
> works but why can't I capture the standard out?
>
> Thanks,
> John K.

Does your IDL code do any plotting? I didn't think IDL actually opened any
connection to the X server unless you issued a command which initiates graphics.

Anyway, try issuing the command 'unset DISPLAY' before running IDL (assuming
you are using sh/ksh). And, for good measure, in IDL use the command
SET_PLOT,'PS' to change the default display device to PostScript.

--
Nigel Wade, System Administrator, Space Plasma Physics Group,
University of Leicester, Leicester, LE1 7RH, UK
E-mail : nmw@ion.le.ac.uk
Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555

Report message to a moderator

[Message index]

		Re: Problems with long IDL background jobs By: Nigel Wade on Mon, 10 November 2003 01:37
		Re: Problems with long IDL background jobs By: R.Bauer on Sun, 09 November 2003 01:56
		Re: Problems with long IDL background jobs By: R.G. Stockwell on Fri, 07 November 2003 12:01
		Re: Problems with long IDL background jobs By: Nigel Wade on Fri, 07 November 2003 01:52
		Re: Problems with long IDL background jobs By: Craig Markwardt on Thu, 06 November 2003 21:32
		Re: Problems with long IDL background jobs By: R.Bauer on Thu, 06 November 2003 09:11
		Re: Problems with long IDL background jobs By: wmconnolley on Thu, 06 November 2003 09:05

Previous Topic:	Re: Is it possible to change the title of a WIDGET_SLIDER?
Next Topic:	Problem on the location of xtickname

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 15:09:44 PDT 2025

Total time taken to generate the page: 1.27700 seconds