[EMAIL PROTECTED] wrote:
>
> This is very interesting. What I was getting is:
>
> 1. Job prints fine,
> 2. Long pause,
> 3. Postscript error
>
> with no blank page. If I use ps_eoj_at_start@, I get:
>
> 1. Job prints fine,
> 2. *Really* long pause (~10 minutes I think)
> 3. Job prints again
> [. . .]
>
You are getting hit with two related things: timeouts on the 850 and
problems in the connection closing sequence between the Tek 850 and
your spooler.
The 850s (maybe all Phasers) have Job Timeout and Wait Timeout parameters
that you can set via web or front panel. Job Timeout is the max time
the printer attempts to process the job before determining the job is
bad and aborts it. Wait Timeout is the max time the printer waits for
the spooler to send a job before timing out. Check these parameters and
set them to something you can live with. (Long is OK, but NOT unlimited.)
I snooped the interface between our Sun spooler and our 850s. My problem
was that the 850 wanted to write a small PS status message back to the
spooler after the spooler had shutdown its connection. Unless the
spooler stayed up long enough to read the data after it had stopped
transmitting, the 850 thought it had a PS problem, waited for one
of its timeouts, and dumped the job.
LPRng thinks it delivered the job correctly. In most cases the job
prints correctly because the status messages aren't needed to print.
However, the 850 thinks it has an error because it couldn't close
correctly.
This drove me NUTS!!! The "shutdown_appsocket" flag fixed my 850s, I
don't need it for my other Phasers(350s & 360s).
> I grabbed ifhp 3.4.1 and used shutdown_appsocket and everything now
> works fine. BUT, since I didn't have this problem at all with ifhp
> running on a NetBSD 1.4.1 machine, I wonder is the problem really the
> printer, or is it the difference between the BSD and Solaris TCP/IP
> stacks?
>
If you were using the same ifhp code, then I believe it is probably
the stacks.
> By the way, were you printing successfully from Unix clients while the
> Windows clients were having problems? That seems to be a *really*
> wierd thing to be fixed by shutdown_appsocket.
Jobs from Unix that I saw worked. However, most of our image
manipulation software is on PC. It all depends on the Postscript
that is generated. Simple PS level 2 jobs work OK. Some PS level 3
jobs have the problem others don't...
>
> Everything is working now with shutdown_appsocket, I'm just wondering
> why it broke in the first place. For instance, the Solaris box in
> question has YASSP installed, which does some fairly complicated
> network tuning at boot time.
>
My Solaris spooler is straight 2.6 with Sun recommended patches.
I have nothing to compare it to.
--
Jerry Damian | Ford Email: [EMAIL PROTECTED]
Ford Motor Co./RCS Dept. | Internet Email: [EMAIL PROTECTED]
SRL MD 1074 RM 1116 | ph: (313)32-38347 fax: (313)39-04865
Dearborn, MI 48121-2053 | my opinions != Ford's opinions or policy
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
