[cups] Forward jobs to another print server without browsing

[Helge Blischke]

One possibility to do this sort of "incremental moving“ of queues could be:
(1)	to write a script (shell, Perl, Python, or whatever) which gets started on demand
	by inetd or xinetd (whatever is installed on your "old“ print server) tied to port
	e.g. 9100.
	This script prints the jobs it gets as raw jobs to the new print server.

(2)	 to write a script around the socket backend (or a replacement for the socket backend)
	which prepends a sort of comment record to the job data containing
	at least the queue name so that the daemon (1) knows where to forward the print job to.

(3)	change the device uri of the printer to move from the original to
	foobar://127.0.0.1 <foobar://127.0.0.1> 

As the requirements may vary from printer to printer (e.g. if a printer requires a execution
of a special filter specified in the printer’s PPD which needs to talk *with* the printer 
instead of only *to* the printer) it may be necessary to provide printer specific routines
for one or both f the mentioned scripts.

Hope this helps you to get forward.


> Am 11.11.2015 um 22:59 schrieb Collins, David <DavidD.Collins at irco.com>:
> 
> 
> V1.4.x question
> ##################################################
> We have a very larger printer environment and we want to move all the printers to another datacenter environment.
> Printing is very critical in the environment.  In order to not use cups polling/browsing in case of network issues, and timeouts, and not doing a
> big bang approach I wanted to see if the following question is possible.
> 
> Because you can only put one servername in the client.conf  is it possible to forward print jobs from one print server
> To another print server without browsing/polling.  Is it possible to hit the queue on print server #1 and have the queue forward the
> job to the other print server?  This would allow us to slowly migrate the printers to the new environment without risking/testing the large
> Environment at one time.
> 
> Let me know if this is possible
> 
> 
> 
> ________________________________
> 
> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
> _______________________________________________
> cups mailing list
> cups at cups.org
> https://www.cups.org/mailman/listinfo/cups