Closed hey101 closed 11 years ago
How are you launching SiriProxy at boot? I've not had any problems using my method. http://www.youtube.com/watch?v=0z6uKw8Zaas
I'm using that exact method. I attached an image below. It stops immediately at starting siriproxy. I can still use siriproxy or even ssh into the raspberry pi.
Edit: Apparently attaching an image to github from my iPhone didn't work. Here you go:
Did you make any tweaks to the file? Which one are you using. The one with logging enables or the background daemon version?
What error messages do you get when manually launching SiriProxy?
I made no tweaks to the file and I am using the logging one. When I manually launch siriproxy it works fine and there are no errors from my memory.
Use the one without logging.
Elvis
On May 31, 2013, at 20:54, hey101 notifications@github.com wrote:
I made no tweaks to the file and I am using the logging one. When I manually launch siriproxy it works fine and there are no errors from my memory.
— Reply to this email directly or view it on GitHub.
The logging one is only meant for temporary diagnostics.
I changed to the normal one instead of the logging one and it works. Thank you!
The way that I have siriproxy running at bootup on my raspberry pi, causes the entire boot process to freeze. As weird as that really is, it works. Anyhow the only way to continue the boot process is by ssh from another computer and killing the siriproxy process. I thought about making my life easier by making a siri command to kill the proccess using system("sudo killall siriproxy"). I have tried several variations of that command and the only thing that happens is the plugin crashes but it does not stop the server. Is there a way to stop the server by a command from inside a plugin?