- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: LPR.LOG
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 11:46 PM
тАО07-29-2004 11:46 PM
Re: LPR.LOG
But it seems useless to correct entries made manually leading to follow on problems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 02:08 AM
тАО07-30-2004 02:08 AM
Re: LPR.LOG
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 02:26 AM
тАО07-30-2004 02:26 AM
Re: LPR.LOG
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 05:01 AM
тАО07-30-2004 05:01 AM
Re: LPR.LOG
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 05:12 AM
тАО07-30-2004 05:12 AM
Re: LPR.LOG
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 05:24 AM
тАО07-30-2004 05:24 AM
Re: LPR.LOG
I will checked that out ..
Can i just add the LF parameter to these printers ?
Thanks
BRuno
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 05:44 AM
тАО07-30-2004 05:44 AM
Re: LPR.LOG
refer to the other printer who do have lf and do it likewise.
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 05:54 AM
тАО07-30-2004 05:54 AM
Re: LPR.LOG
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 06:01 AM
тАО07-30-2004 06:01 AM
Re: LPR.LOG
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 07:35 AM
тАО07-30-2004 07:35 AM
Re: LPR.LOG
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.