I have NextPVR set up to use the EG exectuable to change channels. It works fine from a command prompt but for some reason nothing seemed to happen when NextPVR issues the same command (I checked the logs and it's identical). EG doesn't even report that it saw a message.
The NextPVR folks suggested that it's a problem with the NRecord service running as a local service trying to talk to EG which is running as the local user. I changed the service to run as the same user that is always logged in (which is an administrator) but still no messages to EG.
When I checked to make sure the EG process was under the same user as NRecord I noticed several instances of EventGhost.exe running. Any time NRecord issues the command line another eventghost process appears. It seems like the command line is spawning a new EG instance instead of sending an event or perhaps the process that is supposed to send the event can't and doesn't exit because of it.
Any ideas how I can get the NRecord service to get a message to EG?
P.S. the command line is:
"C://Program Files/EventGhost/EventGhost.exe -e channel 1 {channel}" the curly braces are replaced with a number - I checked the logs to make sure.
Thanks!
Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
command line not getting to EG
Re: command line not getting to EG
I just installed the network event receiver plugin, and used the eventghost command line option "-n" to successfully feed an event into EG without spawning a new process or any funny business.
eventghost -n localhost:1024 testpassword testevent
EG log...
02:14:12 TCP.testevent ['127.0.0.1']
eventghost -n localhost:1024 testpassword testevent
EG log...
02:14:12 TCP.testevent ['127.0.0.1']
Re: command line not getting to EG
That sounds great. I'll try it out tonight!
Re: command line not getting to EG
Took me longer to try than I planned but it works perfectly. About the only issues I had were:
- I HAD to create a password in the plugin. Leaving it blank didn't work as the receiver still takes the first argument as a password and tries to compare it to the blank, tossing an MD5 error. Not that it's a hardship in any way, just not expected.
- The IP is added to the front of payload supplied to the script so I had to change the script (written for a -event) to use the second and third arguments. Again, not a hardship at all, just had to realize it was happening.
I'm a happy puppy now!
- I HAD to create a password in the plugin. Leaving it blank didn't work as the receiver still takes the first argument as a password and tries to compare it to the blank, tossing an MD5 error. Not that it's a hardship in any way, just not expected.
- The IP is added to the front of payload supplied to the script so I had to change the script (written for a -event) to use the second and third arguments. Again, not a hardship at all, just had to realize it was happening.
I'm a happy puppy now!