[9378] in athena10
Re: [Debathena] #458: Non-BSD CUPS clients should choose the
daemon@ATHENA.MIT.EDU (Debathena Trac)
Fri Jul 6 11:44:37 2012
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: broder@MIT.EDU, jdreed@MIT.EDU
Date: Fri, 06 Jul 2012 15:44:32 -0000
Reply-To:
Message-ID: <057.0496f492444f420f558a4e6548447885@mit.edu>
In-Reply-To: <042.03a5d822a6eb12eda68d6b6152810aff@mit.edu>
Content-Transfer-Encoding: 8bit
#458: Non-BSD CUPS clients should choose the correct server
----------------------+-----------------------------------
Reporter: broder | Owner:
Type: defect | Status: new
Priority: normal | Milestone: The Distant Future
Component: printing | Resolution:
Keywords: | Upstream bug:
----------------------+-----------------------------------
Changes (by jdreed):
* milestone: Precise Beta => The Distant Future
Comment:
OK, I've been thinking a bit more about this. I started writing a
wrapper for cancel(1), but thinking more about it, I'm not sure we want
this, for a couple of reasons:
a) PRINTER has never worked with SysV clients
b) SysV clients have never worked with Hesiod
There's no historical behavior to support here, and we're trying to
convince people who want a Hesiod queue to create a local CUPS queue.
Also, as noted, the SysV commands don't fall easily into the model of
printing-config. For example, "cancel 123" can mean "cancel job 123 on
the default printer" or "cancel the default job on printer 123". If we
suddenly make cancel(1) Hesiod-aware, then the behavior of "cancel 123"
could easily change. And I don't think we want to do that.
I think we also need to have a detailed conversation with Ops about the
future of centrally-maintained print queues.
--
Ticket URL: <http://athena10.mit.edu/trac/ticket/458#comment:7>
Debathena <http://debathena.mit.edu>
MIT Debathena Project
