FYI, you can set a HOST_IP environment variable for the server if you want it to explicitly use a specific address, rather than the detected address
Thanks sub.
I added a HOST_IP environment variable to my launchdaemon (excerpt below) as explained by Martin, and the backend now responds with the correct IP address even if parallels or sonicwall is running.
BTW, Martin, I never could get the launchdaemon to work using the NEXTPVR_DATADIR_USERDATA environment variable (as you can see above, I'm not using it). Instead, I use the UserName key, which has the effect of looking for and storing the .npvr-Data directory in my user's directory. I could not get a launchdaemon to work (only a launchagent) until I did that. Except for the little glitch we have discussed elsewhere, the backend has run rock solid with no user intervention.
Thanks sub.
I added a HOST_IP environment variable to my launchdaemon (excerpt below) as explained by Martin, and the backend now responds with the correct IP address even if parallels or sonicwall is running.
Code:
…
<dict>
<key>PATH</key>
<string>/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin</string>
<key>HOST_IP</key>
<string>x.x.x.x</string>
</dict>
…BTW, Martin, I never could get the launchdaemon to work using the NEXTPVR_DATADIR_USERDATA environment variable (as you can see above, I'm not using it). Instead, I use the UserName key, which has the effect of looking for and storing the .npvr-Data directory in my user's directory. I could not get a launchdaemon to work (only a launchagent) until I did that. Except for the little glitch we have discussed elsewhere, the backend has run rock solid with no user intervention.
