A perfect getaway 2009 part

A perfect getaway 2009 part 1

If Im logged in while the script is running I dont see any figures popping up although thats because I dont have the show command in my script, and I thought that python uses tkinter to display figures. The way that Im creating the figures is, a perfect getaway 2009 part 1 histlist, x ylabely xlabelx close The script requires some initial input, so the way Im running it in the background is Is there a way around this, or do I just have to stay sshd into my machine? can you run vnc session? alternatively, there is XFree NX program, but I never used it. it is like screen for X11 session. Anycorn Mar 14 10 at 20:49 I don t really know much about vnc. I thought it was more for controlling a computer on a local network? I think the problem is with x11 closing, so when I close the vnc session wouldn t it give the same results? Jamie Mar 15 10 at 0:55 It looks like youre running in interactive mode by default, so matplotlib wants to plot everything to the screen first, which of course it cant do. at the top of your script, along with making the backend change. I believe your matplotlib backend requires X Look in your matplotlibrc file to determine what your default is from the error, Im betting TkAgg. To run without X11, use the Agg backend. Either set it globally in the matplotlibrc file or on a script by script by adding this to the python program: I added that line to the beginning of my program but still get the same error message. Jamie Mar 15 10 at 0:49 Sorry if this is a a perfect getaway 2009 part 1 answer, but if youre just running a console session, would screen not suffice? Detachable sessions, etc. This might be a stupid reply to your possibly stupid question: What do you mean by console session, screen, and detachable session? The way I m running this is I m home on my OS X machine VPN then SSH via terminal into my linux box at work. Jamie Mar 15 10 at 13:31 Jamie, the unix screen command allows you to detach from your terminal and then re-attach later. Once you are at the terminal prompt, type screen, launch your program. Now just close out of your SSH client. Next time your reconnect on that box, type screen R and you are back to where you left off. Of course, see the screen manpage for lots more details. Mark Mar 15 10 at 13:58 Mark Oh cool, that sound like it can be really useful. Jamie Mar 15 10 at 14:28 If you are running on a nix OS the problem is your session is terminated and all processes requiring a session are also terminated when you disconnect. More specifically all your processes are sent a SIGHUP signal hang-up. The default handling of SITHUP is to terminate the process. If you want you script to continue it needs to ignore the signal. The easiest way to do that assuming you start your script via the command line it to run it using the nohup command: nohup normally sends standard out and standard error to the file in the current directory. Since youre redirecting already output will not be created. his problem is due to X11 connection failing.