1752277 Members
4716 Online
108786 Solutions
New Discussion юеВ

Re: LPR.LOG

 
Ralf Puchner
Honored Contributor

Re: LPR.LOG

that's one reason why lprconfig is the only supported way.

But it seems useless to correct entries made manually leading to follow on problems.
Help() { FirstReadManual(urgently); Go_to_it;; }
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Hey Guys,

Here is the error that the printer is giving.

ERROR -- read_some_chars: read() failed, error: BAd file number

I am chekcing everything to try to solve this problem.

THanks a lot for your Help..

Appreciate

BRuno
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Bruno,

we need to know, which printer is involved.
That error message is in lor.log?

please check the log files of the printers specified by lf= to see, which printer it is.

Michael
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Hey Michael .

These are the printers that are having the errors. I checked the lpr.log to find that out.

# POA - FX2180 NF
lp8|8|nota:\
:af=/usr/spool/lpd3/nota/acct:\
:if=/usr/local/etc/smbprint:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/nota:
---------------------------------------------
# GRV - LEXMARK Recebimento
lp14|14|receb:\
:af=/usr/spool/lpd3/receb/acct:\
:if=/usr/local/etc/smbreceb:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/receb:
---------------------------------------------
# GRV - HP1600 Sequenciamento
lp15|15|hpseq:\
:af=/usr/spool/lpd3/hpseq/acct:\
:if=/usr/local/etc/smbhpseq:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/hpseq:

But notice that all of these printers do not have the LF parameter.

THanks a lot again for your pacient.

REgards

Bruno
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Bruno,

that's something to work on. All of these printers do not have a device to print to. You may want to add the lf option to give it at least a chance to express itself. Also find out, if this isn't just junk entries and kick them out or redo them, if someone needs them.

Michael
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Michael,

I will checked that out ..

Can i just add the LF parameter to these printers ?

Thanks

BRuno
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Bruno,

refer to the other printer who do have lf and do it likewise.

Michael
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Michael i have a new question .
If you have time please help me out.

What is the lock file under the printer directory ?
I also have thi message about lock file.
DEBUG -- printjob: got lock on file 'lock' .Why is this ? do you know ?

THanks

Bruno
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Bruno,

in order to avoid 10 lpd printing the same file, only the one, who gets the lock file, is allowed to handle a queue, see man lpd

Michael
Ralf Puchner
Honored Contributor

Re: LPR.LOG

Bruno,

If you use the supported way next time there would be no problem at all, missing parameters are not possible by using the setup tools delivered with the OS and you will get support.

The "..read.." error message is typically a communication setup problem as written before. The lf parameter is such a parameter necessary for communication.

Help() { FirstReadManual(urgently); Go_to_it;; }