On Tue, May 3, 2011 at 7:13 PM, Kevin LaTona <[email protected]> wrote:
> > I think it might have something to do with the SSH call that is creating a > headless / background process. > I'm not sure what you mean by that...ssh isn't responsible for creating a long-lived process. Standard unix procedure is to have your process either get launched from inetd (or some similar service controller), or daemonize yourself. Are you actually detaching from your parents and the controlling terminal, or just running as a background process (bash '&')? The latter isn't sufficient to outlive the controlling (psuedo)terminal. Check out: http://code.activestate.com/recipes/278731-creating-a-daemon-the-python-way/for the code necessary to do the whole detaching jig according to the rules. (many of which may be optional or unnecessary in some cases, but should be followed for portability and consistency.)
