Guys,
This is part of an ongoing problem I've been looking into. The
job prints ok, but returns an error to ifhp, so ifhp returns JFAIL,
so lpd retries (if you have send_try set to more than 1). I finally
dug out the packet sniffer and got busy, comparing a problem printer
with an identical printer that works fine. Each printer was sent a
plain text job containing "This is a test...".
The data sent from the server (a linux server called 'full') was
identical in both cases. The data returned, however, differed a
little:
How it should work (printername: green_b):
full to printer:
04 25 21 50 53 2D 41 64 6F 62 65 2D 32 2E 30 0A .%!PS-Adobe-2.0.
2F 70 7B 70 72 69 6E 74 7D 64 65 66 20 28 20 25 /p{print}def ( %
25 5B 20 70 61 67 65 63 6F 75 6E 74 3A 20 29 20 %[ pagecount: )
70 0A 73 74 61 74 75 73 64 69 63 74 20 62 65 67 p.statusdict beg
69 6E 20 70 61 67 65 63 6F 75 6E 74 20 65 6E 64 in pagecount end
20 32 30 20 73 74 72 69 6E 67 20 63 76 73 20 70 20 string cvs p
0A 28 20 5D 25 25 20 29 20 70 20 28 29 20 3D 20 .( ]%% ) p () =
66 6C 75 73 68 0A 04 flush..
printer to full:
04 .
printer to full:
04 .
printer to full:
20 25 25 5B 20 70 61 67 65 63 6F 75 6E 74 3A 20 %%[ pagecount:
33 35 36 36 34 35 20 5D 25 25 20 0D 0A 356645 ]%% ..
How it works on printer orange_b (the problem printer):
full to printer:
04 25 21 50 53 2D 41 64 6F 62 65 2D 32 2E 30 0A .%!PS-Adobe-2.0.
2F 70 7B 70 72 69 6E 74 7D 64 65 66 20 28 20 25 /p{print}def ( %
25 5B 20 70 61 67 65 63 6F 75 6E 74 3A 20 29 20 %[ pagecount: )
70 0A 73 74 61 74 75 73 64 69 63 74 20 62 65 67 p.statusdict beg
69 6E 20 70 61 67 65 63 6F 75 6E 74 20 65 6E 64 in pagecount end
20 32 30 20 73 74 72 69 6E 67 20 63 76 73 20 70 20 string cvs p
0A 28 20 5D 25 25 20 29 20 70 20 28 29 20 3D 20 .( ]%% ) p () =
66 6C 75 73 68 0A 04 flush..
printer to full:
25 25 5B 20 45 72 72 6F 72 3A 20 75 6E 64 65 66 %%[ Error: undef
69 6E 65 64 3B 20 4F 66 66 65 6E 64 69 6E 67 20 ined; Offending
43 6F 6D 6D 61 6E 64 3A 20 14 04 04 5D 25 25 0D Command: ...]%%.
0A .
For those wondering, 04 hex is ^D. What you see is that on
the working printer, it for some reason sends two ^D's to
the server. The problem printer doesn't do this (why not?),
and then bombs out with an error.
Can anyone shed any light at all here on what is going on?
What is the purpose of the ^D's being sent to the server?
Why is one printer handling the request for the pagecount ok,
and the other printer (same make & model - Lexmak Optra T616)
dies on it?
Any suggestions?
Anyone?
(can you tell I'm desperate?)
Regards,
Ashley
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
