For the timeout it is most important that it is well more than the 10
seconds which is the check interval of cups-daemon for removing a print
queue which is scheduled for removal but still in use. If CUPS starts up
quickly enough, the 30 seconds should be OK, but best is trying out.
--
You receiv
* can the $UPSTART_FDS still be gotten even if $UPSTART_EVENTS is not
socket? That way we could add some other start event and still get
socket activation.
No, it cannot. UPSTART_FDS is a variable provided by an event type
socket only.
* "or usb-device-added ID_MODEL=USB_Printer"
That could be a
Cameron, puttin 1:30 min as idle timeout is no problem, for your other
questions Dimitri will probably have an answer.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1276713
Title:
upsta
Three comments about this:
* can the $UPSTART_FDS still be gotten even if $UPSTART_EVENTS is not
socket? That way we could add some other start event and still get
socket activation.
* If so, would it be a good idea to add a "or usb-device-added
ID_MODEL=USB_Printer" to the start on, to make the
Remaining problems fixed in cups 1.7.1-5ubuntu6. Thank you, xnox, for
the patch!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1276713
Title:
upstart socket activation for cups
Status
** Changed in: upstart
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1276713
Title:
upstart socket activation for cups
Status in Upstart:
Invalid
To get the on-demand daemon use concept described in the Blueprint
https://blueprints.launchpad.net/ubuntu/+spec/client-1305-printing-
stack-with-mobile-in-mind
working, we need working socket activation in Upstart as this is the
most convenient and well tested (on Mac OS X this is standard) way
This bug was fixed in the package cups - 1.7.1-4ubuntu1
---
cups (1.7.1-4ubuntu1) trusty; urgency=low
* cupsd-upstart-support.patch: Allow starting cupsd socket-triggered
through Upstart, for on-demand starting to save resources (especially
on mobile devices, LP: #1276713).
Uploaded cups 1.7.1-4ubuntu1 with the changes needed on CUPS to Trusty.
** Changed in: cups (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/b
Committed cups 1.7.1-5 to the Debian GIT repository of CUPS. This
contains the changes on cupsd to support triggering the daemon by the
Upstart socket bridge and in addition changes for cupsd to terminate if
it gets idle (no jobs, no shared printers). The package will appear in
Trusty as soon as it
Note that the package does not contain the Upstart config file changes
of the debdiff attached to this bug, to keep user's systems working.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/12
** Tags added: patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1276713
Title:
upstart socket activation for cups
Status in Upstart:
Confirmed
Status in “cups” package in Ubuntu:
** Also affects: cups (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart
Status: New => Confirmed
** Changed in: cups (Ubuntu)
Status: New => Confirmed
** Changed in: upstart
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: cups (Ub
13 matches
Mail list logo
