mirror of
https://github.com/Finb/bark-server.git
synced 2026-04-26 14:15:56 +03:00
[GH-ISSUE #198] SIGQUIT: exit signal does not handle properly #92
Labels
No labels
enhancement
in progress
need test
pull-request
v2
v2
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bark-server#92
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kmahyyg on GitHub (Feb 7, 2023).
Original GitHub issue: https://github.com/Finb/bark-server/issues/198
Service:
Logs:
@mritd commented on GitHub (Feb 7, 2023):
It looks like you are using Systemd to stop bark-server? If you want to exit the program, please do not use the QUIT signal.
The QUIT signal is used to get the process core dump file, if you are debugging on mac you can refer to https://nasa.github.io/trick/howto_guides/How-to-dump-core-file-on-MacOS.html
If you just want to stop the application, you don't need to set the ExecStop option, or you can use the SIGINT signal.
https://www.freedesktop.org/software/systemd/man/systemd.kill.html#KillSignal=
@kmahyyg commented on GitHub (Feb 7, 2023):
ouch. now I understand. It seems that I have some misunderstanding of those signals. Thanks for your response.