[6488] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: ceres/bias switching to CUPS

daemon@ATHENA.MIT.EDU (Evan Broder)
Mon Nov 2 18:16:19 2009

MIME-Version: 1.0
In-Reply-To: <alpine.DEB.1.10.0911021749520.2633@dr-wily.mit.edu>
Date: Mon, 2 Nov 2009 18:16:10 -0500
Message-ID: <2706d8dd0911021516u337f6d38raf670b0fc2810196@mail.gmail.com>
From: Evan Broder <broder@MIT.EDU>
To: Geoffrey Thomas <geofft@mit.edu>
Cc: "Mark W. Manley" <mmanley@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

On Mon, Nov 2, 2009 at 6:05 PM, Geoffrey Thomas <geofft@mit.edu> wrote:
> Is there a way to get timestamps (and if possible hostnames) in CUPS' lpq
> output?
>
> Clicking on "show all jobs" from http://printers.mit.edu:631/printers/ceres
> redirects me to the backend server, which does give me a list over the web.
>
> Neither cups-lpq -Pceres or CUPS_SERVER=printers.mit.edu cups-lpq -Pceres
> seem to work. Setting CUPS_SERVER to the actual backend server gives me a
> listing that, with -l, is the same as mit-lpq's, and without -l is more
> concisely formatted but contains the same information. None of these list
> the timestamp.

I got lpq -h printers.mit.edu -Pceres to work, although I actually
wanted lpr -h full-contact-origami.mit.edu ...

> I'd probably be okay with timestamps only showing up in the web interface,
> but it would be much nicer if we could get lpq to show this.
>
> Also, from the workstation side, do we need to worry about cups-lpq -Pceres
> not working when we do eventually drop LPRng from clients?

Yes. FIIK what a good answer is.

Also, Mark, what do I need to do to punt jobs from queues? I tried to
remove jobs from ceres today with `lprm -h
full-contact-origami.mit.edu -Pceres JOB_NO`, and got "lprm:
Unauthorized" in response. I ended up with a
IPP/full-contact-origami.mit.edu service ticket, so something was
trying to do Kerberos.

- Evan

home help back first fref pref prev next nref lref last post