touch-packages team mailing list archive

[Alexey Zagarin <1273907@xxxxxxxxxxxxxxxxxx>]

Also had this issue.

The problem here is that one or some of the configuration utilities
(could be hplip tools also) restarts cups at some point by calling
/etc/init.d/cups restart. Since cups startup scripts were converted to
upstart jobs, at the moment of restart upstart will notice that there is
no more daemon running and will start it. So does old Sys V script. You
could easy reproduce the problem by issuing /etc/init.d/cups restart
from command line. The result will be two instances of cupsd running.

The solution is simple: get rid of old init scripts and create symlinks
to /lib/init/upstart-job in init.d.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1273907

Title:
  multiple cups daemons running

Status in “cups” package in Ubuntu:
  Expired

Bug description:
  On 13.10, after using system-config-printer, there will be multiple
  cups daemons running:

  root     10159     1  0 17:06 ?        00:00:00 /usr/sbin/cupsd -C /etc/cups/cupsd.conf
  root     10163     1  0 17:06 ?        00:00:01 /usr/sbin/cupsd -F

  Upstart only knows about the one with -F:

  # service cups stop
  cups stop/waiting
  root@terra:~# ps -ef | grep cups
  root     10159     1  0 17:06 ?        00:00:00 /usr/sbin/cupsd -C /etc/cups/cupsd.conf

  This seems to cause all kinds of problems, mostly with them fighting
  over the printers.conf file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1273907/+subscriptions