[6534] in Release_7.7_team
Re: lprm for normal users doesn't work
daemon@ATHENA.MIT.EDU (Mark W. Manley)
Mon Nov 23 09:44:08 2009
Date: Mon, 23 Nov 2009 09:43:57 -0500 (EST)
From: "Mark W. Manley" <mmanley@MIT.EDU>
To: Matthew S Goldstein <austein@mit.edu>
cc: Geoffrey Thomas <geofft@mit.edu>, ops@mit.edu, release-team@mit.edu,
debathena@mit.edu
In-Reply-To: <Pine.LNX.4.64L.0911230933270.11891@way-mo-money.mit.edu>
Message-ID: <alpine.DEB.2.00.0911230938310.30071@green-arrow.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: -2.599
X-Spam-Flag: NO
Whom would you like notified? It can send a zephyr to wherever.
The other case right now that should, eventually, go away where jobs are
being trapped in queue are people sending jobs to Kerberos-enabled LPRng
queues from the CUPS servers. Because they don't speak the same language,
the user can submit the job and it will languish in the CUPS servers'
queues until they're cancelled since they can't get into the LPRng
servers. You'd be surprised how many jobs are getting cancelled for
printers like ashdown and money that currently have no hope of actually
being printed until their conversion to CUPS.
You'd also be surprised at how long queues are getting in just a day.
Ceres, for instance, seemed to have built up a good number of jobs
submitted in just a couple of hours that weren't printing due to some
printer problem. I think for the CLUSTER printers, you'll still see a
significant buildup. It's just a matter of keeping the buildup from
getting too large.
-MM
On Mon, 23 Nov 2009, Matthew S Goldstein wrote:
> Is there some sort of notification sent when it does this? I usually only
> see jobs that old when something is wrong with the printer (even if it just
> needs a reboot), frequently noticing because the queue is so long.
>
> On Mon, 23 Nov 2009, Mark W. Manley wrote:
>
>> I also should mention that I wrote a "queue hoover" as I call it to
>> automatically dequeue and remove any print jobs over a day old from all the
>> queues. This way, print jobs don't linger until some kind operator removes
>> them. I wish that the CUPS feature to just remove defunct jobs worked, but
>> I wish for a lot of things.
>>
>> That job should run hourly and should help in keeping the queue clutter
>> down.
>>
>> -MM
>>
>>
>
