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
Cups shutdown is not working cleanly #3679
Comments
CUPS.org User: jpopelka More info with proposed patch is here: |
CUPS.org User: andrea Thanks a lot, this patch fixes the bug for me. |
CUPS.org User: mike Fixed in Subversion repository. The proposed change in bugzilla is no good - we don't want to stop the printer since that change can get unintentionally saved in printers.conf. An alternate patch is attached which tracks whether we are shutting down and doesn't start new jobs automatically if so. |
CUPS.org User: jpopelka Just a small remark. You misplaced comment I think you now need to swap comments |
CUPS.org User: jpopelka Oh, forget it, I'm wrong. |
"str3679.patch": Index: scheduler/job.c--- scheduler/job.c (revision 9306)
Index: scheduler/main.c--- scheduler/main.c (revision 9306)
cupsdStopServer(); #ifdef HAVE_LAUNCHD |
Version: 1.4.4
CUPS.org User: andrea
Cups is compiled with ./configure, make, make install on a standard ubuntu 9.04 installation.
Add a printer, e.g. a socket printer, disconnect the printer and print a testpage.
If now cups is killed or restarted, some thousend backend and some cups processes appear in top, all are zombie processes.
This happens also with cups 1.4.3, but I had no problems with 1.4b1.
The text was updated successfully, but these errors were encountered: