-
Notifications
You must be signed in to change notification settings - Fork 126
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
[1.28.1] cups-browsed gets SIGKILL during service restart #298
Comments
My guess is correct, reverting the commit which moved signal handling into |
@tillkamppeter signal handler with |
Fixed in commit 23a9dc4 on master. Thank you very much for your report. |
@tillkamppeter Thank you for the fix! Isn't the issue serious enough to release 1.28.2? If someone installs 1.28.1 without the patch, then shutdown will be longer for that 1m 30s till SIGKILL kills cups-browsed. |
I will catch some more bug fixes and in a few days I will release. |
Hi,
we have a CI test which uses cups-browsed - it is compiled to don't keep generated queues and use RemoteName for created local queues pointing to remote cups queues.
Then I set
BrowsePoll <cups-1.4.2 server>
(I usedBrowseFilter
to simplify things too), wait for queues to show up and then stop the service. Stopping the service takes longer than with 1.28.0 and the service is killed (log from systemctl):Debug log
for loading one queue and
debug log when stopping the service (it takes 1m 30s to stop the service - the SIGTERM signal times out and SIGKILL is sent) are attached.
IMO the issue is the signal is ignored and one commit in 1.28.1 moved signal handlers, so I'll try if reverting that commit will help.
The text was updated successfully, but these errors were encountered: