Forum Discussion
SDK 0.4.3 linux bugs and issues
First of all, please oculus, set up a bug tracker or a mailing list, or something that will facilitate a direct path of communicated bugs and isuses without going through this forum. I'll post a co...
"nuclear" wrote:
Another issue: oculusd is not really a daemon.
It would be useful if oculusd was a daemon. One would start it from init as user nobody or a special user oculus or whatever, and it would sit there forever until applications need it (exactly like a windows "service" does). To do this, oculusd must be able to "daemonize" itself, by double-forking when it starts to shed it's controlling terminal. Then an init script can easily be crated to allow it to start during system bootup..
Are you sure about that? When you run "oculusd --help" you get:
Usage: ./oculusd [options]
Options:
-h | --help Print this message
-p | --pid Location of PID file
-d | --daemonize Daemonize
Have you tried using the command line argument to daemonize it, and are having an issue with it, or did you not realise that the argument was needed?