Michael Fox wrote:
On 11/2/05, *Phil Scarratt* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
wrote:
Michael Fox wrote:
> What printer driver you using on windows for that network queue? Sure
> its not a print driver issue on windows..
>
d [02/Nov/2005:15:21:05 +1100] add_job_state_reasons(0xb7ce3c3c[7], 13)
D [02/Nov/2005:15:21:05 +1100] ProcessIPPRequest: 7 status_code=0
d [02/Nov/2005:15:21:05 +1100] ProcessIPPRequest: Adding fd 7 to
OutputSet...
d [02/Nov/2005:15:21:05 +1100] WriteClient: Removing fd 7 from
OutputSet...
D [02/Nov/2005:15:21:05 +1100] [Job 13] LPGETSTATUS returned a port
status of 8C...
W [02/Nov/2005:15:21:05 +1100] [Job 13] Printer off-line.
I [02/Nov/2005:15:21:05 +1100] [Job 13] Sending print file, 8192
bytes...
.
<SNIP>
.
I [02/Nov/2005:15:21:05 +1100] [Job 13] Sending print file, 140099
bytes...
I am more curious why after LPGETSTATUS we see Printer off-line.
Hrmm.. hopefully someone who has more experience with CUPS can tell you
whats happening.
Yewah, I ws somewhat curious also, but had forgotten/ignored it as the
file is sent anyway????
I'll try comparing to a log of a print job from the local Centos box.
Fil
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
