[cups-devel] In reference to: http://www.cups.org/pipermail/cups-devel/2008-April/007718.html

[David Block]

We're running into a similar problem. It was easily solved when printing
over USB by sending a command after every print job to return a one-byte
status command, and the hanging around while timing out quickly went away.
However, it seems that CUPS is waiting for a status return when using this
same printer via RAW TCP/IP on Port 9100. The spooler stays on the Dock for
quite a while at the end of a print job before going away (as it did with
USB), and since Port 9100 isn't Bi-Di, it won't know if we return a status
byte or not.  Is there a configuration that can disable this "wait for
end-of-job status byte" that CUPS is wanting, or a preferred way to do this
when using Port 9100?