Hi list, Correctly starting Virtuoso on Mac OS X with launchd (a .plist) fails. Virtuoso-t starts, that is not the problem.
But the process cannot be controlled any further with launchctl commands. When looking further into launchctl, you see that the originally start process died, and a new one is created: [user@dev ~]$ sudo launchctl list PID Status Label <snip> 12378 - 0x10031fb20.anonymous.virtuoso-t - 0 com.openlinksw.vos <snip> My guess is that virtuoso forks itself. Forking is not good behavior when starting processes with launchd, see launchd.plist documentation: <http://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/man5/launchd.plist.5.html> It is like watchdogd, and shares watchdogd's requirement that processes do not attempt to fork or daemonize on their own. If a process goes into the background launchd will lose track of it and attempt to relaunch it. Which parameter is available to start virtuoso in a non-forked/daemonized way? Thanks, ~Ceriel
