On large networks, with shared CUPS servers, it might be desirable not to
start the gnome-cups-icon which regularly polls the CUPS server for the
status of jobs.
gnome-cups-icon is launched by gnome-session by default, but this is
configurable via gnome-session-properties.
gnome says that it's a cupsys problem. It's true, but this is not a reason to not fix the client part.
Even a malfunctionned server should lead a client to eat all cpu, isn't it ?
Thanks Johnathon, that's a useful comment.
I also found this from debian :
Disabling gnome-cups-icon ======= ======= ====
=======
On large networks, with shared CUPS servers, it might be desirable not to
start the gnome-cups-icon which regularly polls the CUPS server for the
status of jobs.
gnome-cups-icon is launched by gnome-session by default, but this is properties.
configurable via gnome-session-
gnome says that it's a cupsys problem. It's true, but this is not a reason to not fix the client part.
Even a malfunctionned server should lead a client to eat all cpu, isn't it ?