From: Pascal Obry <pascal@obry.net>
To: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] CUPS STR #4521: Unexplained high CPU use by cupsd on Linux...
Date: Tue, 02 Dec 2014 20:43:57 +0100 [thread overview]
Message-ID: <1417549437.5922.28.camel@obry.net> (raw)
In-Reply-To: <8ACDAB6F-4D54-4AA5-9C08-51D013D0CB39@apple.com>
Le mardi 02 décembre 2014 à 11:35 -0500, Michael Sweet a écrit :
> 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?
Isn't this that the issue with the /tmp filling bug?
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1156398
There was a similar bug reported on Debian.
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imagination
http://v2p.fr.eu.org
http://www.obry.net
gpg --keyserver keys.gnupg.net --recv-key F949BD3B
next prev parent reply other threads:[~2014-12-02 19:43 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 [this message]
2014-12-02 20:46 ` Michael Sweet
2014-12-02 19:59 ` Till Kamppeter
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=1417549437.5922.28.camel@obry.net \
--to=pascal@obry.net \
--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.