From: Till Kamppeter <till.kamppeter@gmail.com>
To: printing-architecture@lists.linux-foundation.org
Cc: Didier Raboud <odyx@debian.org>
Subject: Re: [Printing-architecture] CUPS STR #4521: Unexplained high CPU use by cupsd on Linux...
Date: Tue, 02 Dec 2014 20:59:03 +0100 [thread overview]
Message-ID: <547E1A07.7020900@gmail.com> (raw)
In-Reply-To: <8ACDAB6F-4D54-4AA5-9C08-51D013D0CB39@apple.com>
On 12/02/2014 05:35 PM, Michael Sweet wrote:
> All,
>
> We've received several bug reports about cupsd using 100% CPU, either on startup or after connecting/turning on a printer:
>
> https://www.cups.org/str.php?L4521
>
> I cannot reproduce myself, but was hoping someone more familiar with all of the helper programs running on Linux might be able to shed some light on this?
>
We (Didier Raboud and me) did not yet update Debian and Ubuntu to CUPS
2.0.x. Therefore we did not hit the problem yet.
Till
prev parent reply other threads:[~2014-12-02 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 16:35 [Printing-architecture] CUPS STR #4521: Unexplained high CPU use by cupsd on Linux Michael Sweet
2014-12-02 19:43 ` Pascal Obry
2014-12-02 20:46 ` Michael Sweet
2014-12-02 19:59 ` Till Kamppeter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=547E1A07.7020900@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=odyx@debian.org \
--cc=printing-architecture@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.