[6510] in Release_7.7_team
Re: ceres/bias switching to CUPS
daemon@ATHENA.MIT.EDU (Evan Broder)
Mon Nov 16 09:04:34 2009
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.00.0911160856210.15979@green-arrow.mit.edu>
Date: Mon, 16 Nov 2009 09:04:18 -0500
Message-ID: <2706d8dd0911160604k270b7deat67aaeb0b67e5ae6b@mail.gmail.com>
From: Evan Broder <broder@MIT.EDU>
To: "Mark W. Manley" <mmanley@mit.edu>
Cc: Geoffrey Thomas <geofft@mit.edu>, release-team@mit.edu, ops@mit.edu
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Flag: NO
X-Spam-Score: 0.00
Content-Transfer-Encoding: 8bit
Yeah, I agree, and I think we can do that. add-athena-printer would
run on users' workstations and configure a printers.mit.edu queue
there. The intent was allowing users to easily add a particular queue
to their picklist without having to go through a cups.mit.edu (or
whatever-print-server-we're-using-now.mit.edu) admin.
- Evan
On Mon, Nov 16, 2009 at 9:02 AM, Mark W. Manley <mmanley@mit.edu> wrote:
> I'd still like to keep the plan of:
>
> printers.mit.edu - all printers, regardless
> cluster-printers.mit.edu - DORM and CLUSTER only
>
> so that we don't end up with a huge mess on our hands (it's not called
> "I-want-the-smaller-list-of-printers-lolz.mit.edu"). The only change that I
> would make, if needed, to printers is to allow people to drop their printers
> from listing all together. That way, people won't accidentally select
> printers whose owners would rather not have them selected.
>
> The question comes of why people wanted to have their printers selectable on
> cups. I suspect they just wanted to be able to use CUPS from their machine,
> not to be treated specially, but that could be an incorrect assumption.
>
> I'm also unclear about where the "add-athena-printer" script runs. It is
> that something that runs on the desktop that simply creates a pointer to the
> printers.mit.edu queue?
>
> -MM
>
> On Sat, 14 Nov 2009, Evan Broder wrote:
>
>> I've got a changeset in -proposed now to point all cluster machines
>> directly at printers.mit.edu. I think that should be ready to deploy
>> to the clusters on Monday.
>>
>> Since there are queues currently being served by cups.mit.edu that
>> aren't DORM or CLUSTER (we added a few on request), I'd like to have
>> an easy means for users to add those. We've discussed having an
>> "add-athena-printer" script that would do something sufficiently
>> clever, and it shouldn't be hard to write.
>>
>> Once we have that available, I'm definitely ready to re-point
>> everybody else at cluster-printers.mit.edu and/or let you guys steal
>> the cups.mit.edu name. Hopefully we can do this within the next week
>> or two.
>>
>> - Evan
>
