I'm currently launching the process using nohup but occasionally after logging out and back in again the process is gone. Something is reaping it. I don't need it to survive a reboot (so I think launchd might be overkill here), but I would like it to persist as long as the machine is up and running, whether I'm logged in or not.

link|improve this question

I think this question is better suited for StackOverflow. – Daryl Spitzer Nov 9 '10 at 15:32
feedback

2 Answers

up vote 1 down vote accepted

Check out Lingon. It is a very easy to use GUI with which you can edit and create launchd configuration files.

link|improve this answer
This makes the barrier to launchd entry low enough to use for this case. Thanks. – Ian C. Nov 10 '10 at 16:53
feedback

screen? You can log out, and the screen sessions continue running. Although they shouldn't count on your FileVault home directory being mounted, if you use that feature.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.