Mailinglist Archive: opensuse (5100 mails)
| < Previous | Next > |
Re: [SLE] CUPS weird behavior (Apologize for the length of this email )
- From: Johannes Meixner <jsmeix@xxxxxxx>
- Date: Fri, 18 Jun 2004 09:21:55 +0200 (CEST)
- Message-id: <Pine.LNX.4.58.0406180844190.23119@xxxxxxxxxxxxx>
Hello,
On Jun 17 10:25 Marshall Heartley wrote (shortened):
> I can que individual jobs just fine and when they are completed, I
> can print another document. But I cannot have one document printing
> and que another one up behind it! Every program states that the job
> is accepted and is being qued. But lo and behold when the first job
> is done, there is nothing but silence from the printer!
...
> I am using the CUPS that comes with SuSE 9.1 and have a Epson Stylus
> Color 880 printer attached to the network with a small Netgear print
> server.
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).
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).
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.
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.
Regards
Johannes Meixner
--
SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@xxxxxxx
90409 Nuernberg, Germany WWW: http://www.suse.de/
| < Previous | Next > |