[cups.general] Help BrowseRemoteOptions

[Steve Smith]

> ...

> Because the client will wait for the first job to complete before 

> sending the next...

> 

> Ok I can see some kind of logic to this but if the client jobs stay on 

> the client while the first job completes on the server when I power 

> cycle the client machine the outstanding jobs disappear from the 

> client.  Is there any way to make all the client jobs for the same 

> queue go to the server and not sit on the client ?

 

If you don't have any local queues, you can point the clients directly at
the server in /etc/cups/client.conf:

 

     ServerName yourserver

 

If you have multiple servers and/or local queues, use:

 

     BrowseRemoteOptions waitjob=no

 

to let the client send the job and then go on to the next one.  For
hard-wired remote queues just add "?waitjob=no" to the end of the device
URI.

 

I've added the BrowseRemoteOptions as described above in the client machine
client.conf file but it doesn't appear to have any effect unless I also set
the ServerName in the client client.conf file.  I didn't want to define the
servername as we plan to have multiple servers deployed in regional and
international offices. 

 

I can now get the client to pass multiple jobs to the server but for some
strange reason the server will take maybe 3 or 5 or 6 (random) jobs and then
no more until one of those already in the server queue is cancelled or
completed.

 

Steve Smith - GEO Designs Limited

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cups.org/pipermail/cups/attachments/20090722/98a01468/attachment-0001.html>