-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd notify: Fail to understand how to properly launch this service through systemd #42
Comments
To elaborate, this is the systemd wrapper of the "old" voice service;
So to convert this into;
However I do not see which hooks need to be changed to what? |
sdnotify in dinkum listener will report to the service |
We need to let systemd know it was started, which is done with sending READY=1 with sdnotify package. I don't see it imported anywhere within Dinkum listener so we still need to do it with the wrapper. Otherwise systemd keeps restarting the service when the timeout is reached. What you stated is just a type=simple not type=notify |
This is my service file. And corresponding file Don't know if this is correct either |
Are you sure the voice service does not get restarted after the timeout of 1 minute? If this work, I am even more confused. Then somewhere within the dinkum code, it talks to systemd without importing any sdnotify package. ??? |
This has been working for me in Neon images; I just pass the callback methods to init as usual: |
@jinx you are right, i was somewhat hallucinating and under the impression those were there. we can work with the default callback handler here and notify from there
The mention in the dinkum code (watchdog) is a lambda function that is doing nothing further check: |
OH. I missed the signature change; |
to avoid confusion i was reffering to
ie the default |
So what should the service file, and exec file be? Similar to listener? |
I fail to understand how to launch this with systemd as type=notify
Can someone point me to the right way? Or better explain me what, where, how, etc.
The text was updated successfully, but these errors were encountered: