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 delay of CUPS starting even more invisible to the user? (WARNING: have not confirmed that USB_Printer ID_MODEL can be relied upon consistently, that is just what I got in upstart monitor when I plugged in my printer). * Finally, I think the default exit on idle should be more than 30 seconds; more like a minute, maybe 1:30. This would have big benefits to the UX with a tiny impact on battery life IMO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276713 Title: upstart socket activation for cups To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1276713/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
