Mailinglist Archive: opensuse (5100 mails)
| < Previous | Next > |
Re: [SLE] CUPS weird behavior (Apologize for the length of this email )
- From: "Marshall Heartley" <marshall.heartley@xxxxxxxxxxxxx>
- Date: Fri, 18 Jun 2004 05:54:58 -0400
- Message-id: <000701c4551a$51833340$0200a8c0@taz>
> Test to connect it directly via the first parallel port.
> I hope you have a hardware architecture with a parallel port
> (and not for example an IBM Z-Series).
I will try later and do this but in 9.0 this worked flawlessly with
the current setup.
> What I have in mind is:
>
> Either
> the backend which runs for the first job doesn't finish
> at all because it waits forever for something which is never
> sent from this printserver box but this seems not to be the case
> because otherwise it woudn't work to print the next job
> after the first was finished
> or
> the backend finishes with a non zereo exit code and the
> queue becomes disabled by the cupsd but this seems not to be
> the case because otherwise it woudn't work to print the next
> job after the first was finished
> or
> the backend finishes with zereo exit code and immediately
> after this the next job is sent to this printserver box
> but the printserver box gets confused about so much data
> or so many jobs or whatever this kind of hardware
> may not like and then this printserver box discards
> the data (i.e. it discards the next job).
Well like I have stated earlier, I did not have an issue with this
before. Since there is a limit to the size of the messages that I can
post, I can send to you directly a copy of the error_log amd maybe
this can tell you what is going on?
> Read the Administration Manual about printserver boxes.
> Do not blame first of all the CUPS software when you may have
> broken hardware or a broken lpd implementation in your
> printserver box.
Again it worked with previous versions of SuSE and Windows flawlessly!
> If you don't access your printserver box via direct TCP socket
> (as far as I remember you didn't tell how you access it)
> try to access your printserver box via direct TCP socet.
> Read the Administration Manual about printserver boxes.
Yes, this is how I access my printer. I use socket 9100.
Like I stated, if printed individually, the setup is fine but trying
to print multiple different jobs borks up the works.
Marshall
> I hope you have a hardware architecture with a parallel port
> (and not for example an IBM Z-Series).
I will try later and do this but in 9.0 this worked flawlessly with
the current setup.
> What I have in mind is:
>
> Either
> the backend which runs for the first job doesn't finish
> at all because it waits forever for something which is never
> sent from this printserver box but this seems not to be the case
> because otherwise it woudn't work to print the next job
> after the first was finished
> or
> the backend finishes with a non zereo exit code and the
> queue becomes disabled by the cupsd but this seems not to be
> the case because otherwise it woudn't work to print the next
> job after the first was finished
> or
> the backend finishes with zereo exit code and immediately
> after this the next job is sent to this printserver box
> but the printserver box gets confused about so much data
> or so many jobs or whatever this kind of hardware
> may not like and then this printserver box discards
> the data (i.e. it discards the next job).
Well like I have stated earlier, I did not have an issue with this
before. Since there is a limit to the size of the messages that I can
post, I can send to you directly a copy of the error_log amd maybe
this can tell you what is going on?
> Read the Administration Manual about printserver boxes.
> Do not blame first of all the CUPS software when you may have
> broken hardware or a broken lpd implementation in your
> printserver box.
Again it worked with previous versions of SuSE and Windows flawlessly!
> If you don't access your printserver box via direct TCP socket
> (as far as I remember you didn't tell how you access it)
> try to access your printserver box via direct TCP socet.
> Read the Administration Manual about printserver boxes.
Yes, this is how I access my printer. I use socket 9100.
Like I stated, if printed individually, the setup is fine but trying
to print multiple different jobs borks up the works.
Marshall
| < Previous | Next > |