-
Notifications
You must be signed in to change notification settings - Fork 2
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
~/.local/share/sinntp/ documentation #10
Comments
You guessed right; this number is identifier of the last successfully downloaded article. |
Comment submitted by I'll give a little bit more background on why I'm asking this(I should have in my first message). Suppose sinntp is killed with And two more related questions: Thanks |
SIGKILL is almost never the right signal. It should be used only as last resort. SIGTERM is the generic signal for program termination. Unfortunately, sinntp doesn't currently handle it gracefully. This is something that we ought to fix. As a temporary work-around you can use SIGINT, which is handled correctly AFAICT. |
I've opened issue #15 to track SIGTERM handling. |
Issue reported by
randomcoder1
at Google Code:Hi, can you please add more documentation on what the integers in files in ~/.local/share/sinntp/ mean.
My guess is they are intended for sinntp to know where it left off, but I'm not sure.
Also, my apologies if I missed any part of the current documentation that described is.
The text was updated successfully, but these errors were encountered: