Re: cups jobs queue

2017-07-28 Thread Curt 
On 2017-07-27, Brian  wrote:
> On Thu 27 Jul 2017 at 13:06:33 +0200, Pol Hallen wrote:
>
>> ?waitjob=false
>> 
>> thanks :)
>
> A very neat and elegant solution. For those who are mystified or
> wondering what the fuss about:
>
> Pol Hallen has a *local* queue set up with a device_uri like
>
>   ipp://192.168.1.100/printers/E460DN
>
> He meets the problem he has descibed. Changing the device_uri to
>
>   ipp://192.168.1.100/printers/E460DN?waitjob=false
>
> exercises the power of IPP and allows all jobs to be queued on the
> server.
>

Unless the printer isn't idle (waitprinter=false). But I guess that's
extraneous to the problem statement.

-- 
“Certitude is not the test of certainty.”
--Oliver Wendell Holmes, Jr.

Re: cups jobs queue

2017-07-27 Thread Brian 
On Thu 27 Jul 2017 at 13:06:33 +0200, Pol Hallen wrote:

> ?waitjob=false
> 
> thanks :)

A very neat and elegant solution. For those who are mystified or
wondering what the fuss about:

Pol Hallen has a *local* queue set up with a device_uri like

  ipp://192.168.1.100/printers/E460DN

He meets the problem he has descibed. Changing the device_uri to

  ipp://192.168.1.100/printers/E460DN?waitjob=false

exercises the power of IPP and allows all jobs to be queued on the
server.

-- 
Brian.

Re: cups jobs queue

2017-07-27 Thread Pol Hallen 

?waitjob=false

thanks :)
--
Pol

cups jobs queue

2017-07-27 Thread Pol Hallen 

Hi folks :)

It happens that if the printer is off and from client (the printer is 
physically connect to cups server) I send some jobs, only first jobs 
sent to cups server, from second job all remains in the client.


I'd like send all job to cups server, next when I can power-on the 
printer I've all jobs to printing


It happens only with linux client, with windows no problem

any idea?

thanks :)

Pol