id summary reporter owner description type status priority milestone component resolution keywords cc fix_version see_also 985 checking for whether CUPS is running is fragile kaduk "We've recently discovered that we need to check whether CUPS is running in a few places, e.g. when adding printers. The obvious way, using lpstat -r, is actually nontrivial since that command merely prints output, instead of returning a status value of success for running and failure for not-running. Thus, we end up parsing its output, which is fragile to upstream changing that output. It looks like we currently check for CUPS' status in: {{{ config/cluster-cups-config/debian/postinst config/cluster-cups-config/debian/configure-athena-printers }}} but that's just a quick check of the past 300 transactions in source-commits. We should (a) file an upstream bug that lpstat -r should return a usable status code, and (b) try to make our scripts robust to any changes upstream might decide to make." defect new normal Upstream Utopia -- LP:814908