[cups.general] Queues shutting off

[Minatra, Pat H.]

Yes, they go to the state of disabled, accepting and you have to turn
them back up (enable) and everything is fine.

I can probably write a Unix script to do this via cron but I have a
couple that must stay down never be brought up so I will have to allow
for that.

So, am I correct when I say that power cycling will bring the queue
down?

Can I get a confirmation on that as it could be the culprit but I need
to know that in order to pursue that avenue.

As far as:
-----start snip
>  print jobs go to the wrong queues and

That's a new one to me from a CUPS point of view... I've always just
assumed the error was sitting in the seat in front of the computer.
-----end snip

I believe it to be the operator and not a fault of the system; but you
understand why I 'had to ask'.

Thanks for any help and have a GREAT day!


-------------------------
"Life is but a twinkle in the eye of eternity"
"The shortest distance between a problem and a solution is the distance
between your knees and the floor"
"sorrow looks back - worry looks around - faith looks up"
Regards,
Pat H. Minatra - N5GJR
(325) 670-5804 voice
(325) 670-1570 fax
Hardin*Simmons University  
www.hsutx.edu
PO BOX 16040
Abilene, TX  79698

-----Original Message-----
From: cups-bounces at easysw.com [mailto:cups-bounces at easysw.com] On Behalf
Of Paul Ortman
Sent: Friday, February 24, 2006 3:47 PM
To: Mirror of cups.general Newsgroup
Subject: Re: [cups.general] Queues shutting off

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Minatra, Pat H. wrote:
> The queues go down by themselves,

By "go down" do you mean they changed from state "enabled,accepting" to
"disabled,accepting"?  If so, the likely culprit is network transmission
errors or people power cycling the printer.

The hack that works was suggested by Mark Hefferman on the Pykota
mailing list earlier today:

> We've just got a cron job which 
> reenables queues every five minutes on the print server.  Here's the 
> script:
>
> #!/usr/bin/perl
> 
> use warnings;
> use strict;
> 
> my $out = `/usr/bin/lpstat -a -p`;
> (!$?) or die "Error calling lpstat: $!\n";
> while ($out =~ m/(\S+) (disabled|not accepting)/g) {
>     print "Accepting and enabling $1\n";
>     !system("/usr/sbin/accept $1") or warn "Error accepting $1: $!\n";
>     !system("/usr/bin/enable $1") or warn "Error enabling $1: $!\n";
> }


>  print jobs go to the wrong queues and

That's a new one to me from a CUPS point of view... I've always just
assumed the error was sitting in the seat in front of the computer.

- --
Paul Ortman

PGP Key: 55602C81
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFD/37Kfw8KGlVgLIERAl/wAKCL/ZLBC3vm72OumSogfpnUe7MfggCgjxmC
UlcSSN09HRFChOWQIN4Yups=
=DHvd
-----END PGP SIGNATURE-----

_______________________________________________
cups mailing list
cups at easysw.com
http://lists.easysw.com/mailman/listinfo/cups