On Tue, February 23, 2016 10:32 am, John Hodrien wrote:
> On Tue, 23 Feb 2016, Valeri Galtsev wrote:
>
>> Mark, it may depend on how he set up printing. If it is CUPS and it can
>> not connect to LPD or IPP downstream, then that particular queue will be
>> stopped. So, one may need to restart queues after networks outage. The
>> most robust way I know is to have CUPS connect jetdirect (9100). No
>> matter
>> whether there is outage or not, the queue is not stopped... So, it well
>> could be for him to go carefully through configuration in the first
>> place,
>> and figure out what in particular happens due to network outage.
>> Requires
>> some actual sysadmin work ;-)
>
> It'll do whatever you tell cups to do.
>
> ErrorPolicy retry-job/stop-printer/abort-job
>
I usually have a policy to abort the job. This setting, however, still
does not prevent queue stopped if queue talks LPD or IPP downstream, and
there is network problem (i.e. it can not reach downstream device). The
queue isn't stopped _only_ if it talks JetDirect (port 9100 or raw is the
synonym) downstream. No temporary network problems lead to queue stopped
in this last case.
Just my observation.
Valeri
> But none of that should apply when the printer and cups server can see
> each
> other on the network and are behaving (along with normal services like
> DNS),
> irrespective of the state of the network upstream.
>
> jh
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
>
++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
++++++++++++++++++++++++++++++++++++++++
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
