Redirect new print jobs to another queue in CUPS

The local windows spool simply delivers it to the remote spool.

I guess in order for your wish to work (that everybody sees everyone queued stuff) will only work with some Windows Printing Queue, but i am far from a windows expert. I'd look into IPP, i am also not sure if lpd was designed to send the queue back to the client, but rather to only submit your things to the server.

I haven't had any problems with large production printing environments with 100+ printers (running CUPS or LPRng). Is there a reason you're using cups-lpd instead of just using lp/lpr through CUPS?

There are a few CUPS tweaks you can make to ease troubles, though. Depending on your Linux distribution, you will want to change some of the defaults in the /etc/cups/cupsd.conf file.

• I tend to increase the MaxLogSize value to 2000000000.
• You may also want to increase MaxJobs to a value beyond the default 500 (I use 5000) or to 0 (no limit). This details the maximum number of jobs to keep in memory (active and completed). If you have a high-volume device fail or stall, but print jobs continue to be submitted, this number can be reached easily and will stall the entire printing system until the queues are cleared.
• In the /etc/cups/printers.conf, I set the printers' ErrorPolicy directive to retry-job instead of the default stop-printer. This means that small connectivity blips/paper jams/etc. won't result in printers going offline, requiring a cupsenable to resume printing.