Thanks for all the info. The print queues in question look like this: SP-STATUS --> CR2-CLEAN PROG lpr -P cr2 ps -ef --> 15051 tty unknown*1995 19950 jspprint -Jb -Q CR2-CLEAN 36 They were started by root via the the :RESTSPOOLER command and were being printed to by root.
The interesting thing is that it doesn't affect all printers. Some printers print immediately, as would be expected from my experience. We have around 50 print queues and all have worked great on our existing system. The problem has cropped up on a new install. Both run identical operating systems and jbase installs. jdiag -v output is identical. Prior to posting here, I did a search and found a thread suggesting the JBC_DESPOOLSLEEP environment variable. Setting this seemed to have no effect. I set it for the root user, restarted jbase the jbase spooler, re-defined the printer, confirmed that it was still set. And yet printing is still delayed to a select few printers. The reason why immediate printing is so important is that we are printing labels in response to inventory transactions. Non-immediate response really slows down the entire process. -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
