[SuSE Linux] Remote Printing
I am attempting to allow a remote UNIX (non-Linux) to print to my local printer with mixed success. I have been able to configure the remote UNIX box to send me print requests. When I instruct the remote system to send print requests to 'lp1' , the print request arrives in the '/var/spool/lpd/PS_300dpi-letter-ascii-mono-300' directory, with a control and data file. However lpd does not spool it out. When I instruct the remote system to send print requests to 'lp2' or 'lp', the print request arrives in the '/var/spool/lpd/PS_300dpi-letter-auto-mono-300' directory, with a control and data file. However lpd does not spool it out either. When I instruct the remote system to send print requests to 'lp3' , the print request arrives in the '/var/spool/lpd/PS_300dpi-letter-raw' directory, with a control and data file. However lpd does not spool it out either. I have reconfigured '/etc/inetd.conf' to allow tcp connection on port 515 for printing. Line in '/etc/inetd.conf': ======================================================================== printer stream tcp nowait root /usr/sbin/tcpd /usr/bin/lpd -i ======================================================================== Verified port 515 is properly configured for printing in '/etc/services'. Line in '/etc/services' ======================================================================== printer 515/tcp spooler # line printer spooler ======================================================================== Verified that tcp is configured in '/etc/protocols'. Line in '/etc/protocols': ======================================================================== tcp 6 TCP # transmission control protocol ======================================================================== Verified that '/etc/hosts.lpd' file had an entry allowing print requests from the remote UNIX system. Line in '/etc/hosts.lpg': ======================================================================== hpcvsjpg.cv.hp.com ======================================================================== I stopped and restarted inetd after all configuration done. Here is the contents of my '/etc/printercap' file: ======================================================================== ### BEGIN apsfilter: ### PS_300dpi letter mono 300 ### # Warning: Configured for apsfilter, do not edit the labels! # apsfilter setup Thu Nov 5 21:02:57 PST 1998 # ascii|lp1|PS_300dpi-letter-ascii-mono-300|PS_300dpi letter ascii mono 300:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300:\ :lf=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300/log:\ :af=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300/acct:\ :if=/var/lib/apsfilter/bin/PS_300dpi-letter-ascii-mono-300:\ :la@:mx#0:\ :sh:sf: # lp|lp2|PS_300dpi-letter-auto-mono-300|PS_300dpi letter auto mono 300:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/PS_300dpi-letter-auto-mono-300:\ :lf=/var/spool/lpd/PS_300dpi-letter-auto-mono-300/log:\ :af=/var/spool/lpd/PS_300dpi-letter-auto-mono-300/acct:\ :if=/var/lib/apsfilter/bin/PS_300dpi-letter-auto-mono-300:\ :la@:mx#0:\ :sh:sf: # raw|lp3|PS_300dpi-letter-raw|PS_300dpi letter raw:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/PS_300dpi-letter-raw:\ :lf=/var/spool/lpd/PS_300dpi-letter-raw/log:\ :af=/var/spool/lpd/PS_300dpi-letter-raw/acct:\ :if=/var/lib/apsfilter/bin/PS_300dpi-letter-raw:\ :la@:mx#0:\ :sh:sf: # ### END apsfilter: ### PS_300dpi letter mono 300 ### ======================================================================== Any ideas?? jpg@cv.hp.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
John P. Griffin wrote:
I am attempting to allow a remote UNIX (non-Linux) to print to my local printer with mixed success. I have been able to configure the remote UNIX box to send me print requests.
if the jobs appear in your linux queue, things look allright to me. what printing package are you running on your linux box? lpd-old or plp? plp is a bit weird with network printing. In that case, make sure the /dev/lp? ports are rw for all.
When I instruct the remote system to send print requests to 'lp1' , the print request arrives in the '/var/spool/lpd/PS_300dpi-letter-ascii-mono-300' directory, with a control and data file. However lpd does not spool it out.
a "lpc up all" or "lpc up lp1" on you linux box might do some miracular job. ;-)
Here is the contents of my '/etc/printercap' file: ======================================================================== ### BEGIN apsfilter: ### PS_300dpi letter mono 300 ### # Warning: Configured for apsfilter, do not edit the labels! # apsfilter setup Thu Nov 5 21:02:57 PST 1998 # ascii|lp1|PS_300dpi-letter-ascii-mono-300|PS_300dpi letter ascii mono 300:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300:\ :lf=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300/log:\ :af=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300/acct:\ :if=/var/lib/apsfilter/bin/PS_300dpi-letter-ascii-mono-300:\ :la@:mx#0:\
curiosity: what means la@? (didn't see it in the man page)
:sh:sf: #
Any ideas??
Not much more. ;-( what about the other machine's printcap? But I suppose the problem is on the linux machine. Juergen -- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Mon, 16 Nov 1998, Juergen Braukmann wrote:
John P. Griffin wrote:
I am attempting to allow a remote UNIX (non-Linux) to print to my local printer with mixed success. I have been able to configure the remote UNIX box to send me print requests.
When I instruct the remote system to send print requests to 'lp1' , the print request arrives in the '/var/spool/lpd/PS_300dpi-letter-ascii-mono-300' directory, with a control and data file. However lpd does not spool it out.
a "lpc up all" or "lpc up lp1" on you linux box might do some miracular job. ;-)
Also, what does lpc stat say? Can you currently print from the linux? Maybe you just need to start the lpd daemon. You could do this just by entering lpd in a terminal window.. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Thanks for the reply Kyle,
On Mon, 16 Nov 1998, Juergen Braukmann wrote:
John P. Griffin wrote:
I am attempting to allow a remote UNIX (non-Linux) to print to my local printer with mixed success. I have been able to configure the remote UNIX box to send me print requests.
When I instruct the remote system to send print requests to 'lp1' , the print request arrives in the '/var/spool/lpd/PS_300dpi-letter-ascii-mono-300' directory, with a control and data file. However lpd does not spool it out.
a "lpc up all" or "lpc up lp1" on you linux box might do some miracular job. ;-)
Also, what does lpc stat say? Can you currently print from the linux?
Maybe you just need to start the lpd daemon. You could do this just by entering lpd in a terminal window..
Actually, Correct me if I'm wrong, but once a service is configured in inetd.conf the inetd daemon spawns the appropriate TCP interface program, in the case of lpd it is '/usr/sbin/tcpd'. It performs the tcp handshaking with the remote system to get the print data and then passes it off to the /usr/bin/lpd program when done. Therefore the beauty of inetd is it is the only daemon waiting around for something to do, and only fires up lpd, and other like configured programs, in the inetd.conf file when a client comes knocking on the TCP door at the ports configured. Thus 'lpd' is not running on my system at all times. Even if I execute '/sbin/init.d/lpd start', lpd is only alive while data is being sent to the physical printer. It dies after the data transfer is complete, which I believe is expected behaviour. jpg@cv.hp.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
John P. Griffin wrote: Hi John, reading the other answers and you comment about lpd not running i looked into the SDB and found an article: <A HREF="http://localhost/support-db/sdb_e/fehr_lpr_1.html"><A HREF="http://localhost/support-db/sdb_e/fehr_lpr_1.html</A">http://localhost/support-db/sdb_e/fehr_lpr_1.html</A</A>> that could be helpful. LPD must be present all time, if you do a brauki@marvin:/home/brauki > ps ax | grep lpd 232 ? S 0:00 /usr/sbin/lpd 974 p2 S 0:00 grep lpd brauki@marvin:/home/brauki > you must see lpd running. (hopefully helpful, it's a bit older...) if a job "appears" lpd forkes, it's alter ego does the job, the original waits for the next job to appear. In that case, search for reasons that might cause lpd to die. Jürgen -- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Juergen, First off thanks for the reply, your the only one.
John P. Griffin wrote:
I am attempting to allow a remote UNIX (non-Linux) to print to my local printer with mixed success. I have been able to configure the remote UNIX box to send me print requests.
if the jobs appear in your linux queue, things look allright to me. what printing package are you running on your linux box? lpd-old or plp?
No clue, how do I determine this?
plp is a bit weird with network printing. In that case, make sure the /dev/lp? ports are rw for all.
The permissions were 660, I changed them to 666. Then stopped and restarted lpd via the /sbin/init.d/lpd script. No change.
When I instruct the remote system to send print requests to 'lp1' , the print request arrives in the '/var/spool/lpd/PS_300dpi-letter-ascii-mono-300' directory, with a control and data file. However lpd does not spool it out.
a "lpc up all" or "lpc up lp1" on you linux box might do some miracular job. ;-)
I did a "lpc up all" and got a couple of errors: ---------------------------------------------- # lpc up all ascii: printing enabled lpc: connect: No such file or directory couldn't start daemon lp: printing enabled lpc: connect: No such file or directory couldn't start daemon raw: printing enabled lpc: connect: No such file or directory couldn't start daemon ----------------------------------------------
Here is the contents of my '/etc/printercap' file: ======================================================================== ### BEGIN apsfilter: ### PS_300dpi letter mono 300 ### # Warning: Configured for apsfilter, do not edit the labels! # apsfilter setup Thu Nov 5 21:02:57 PST 1998 # ascii|lp1|PS_300dpi-letter-ascii-mono-300|PS_300dpi letter ascii mono 300:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300:\ :lf=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300/log:\ :af=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300/acct:\ :if=/var/lib/apsfilter/bin/PS_300dpi-letter-ascii-mono-300:\ :la@:mx#0:\
curiosity: what means la@? (didn't see it in the man page)
No idea, Yast put it in there for me when I configured the printer. I tried checking it out as well when I was trying to determine where the 2 pages per piece of paper default was set. I found that in '/etc/apsfilterrc' file. This appears to be another undocumented feature.
:sh:sf: #
Any ideas??
Not much more. ;-(
what about the other machine's printcap? But I suppose the problem is on the linux machine.
The other machine is a HP 9000 Series 800 Model T600 running HP-UX 10.20. It uses '/var/spool/lp/interface/<printer>' as a template to invoke the '/usr/sbin/rlp' program to spool to remote printer daemon. This is pretty much a bullet proof system. Since then it has gotten worse on my SuSE 5.3 linux box, now when I attempt to print locally I get: ---------------------------------------- $ ls | lpr lpr: connect: No such file or directory jobs queued, but cannot start daemon. ---------------------------------------- I then have to execute '/sbin/init.d/lpd stop' and then '/sbin/init.d/lpd start' each and every time to print out files. I even removed the '/etc/printcap' and reconfigured in Yast. Same results. Is there another print daemon program/mechanism available that works a little better than the one packaged with SuSE 5.3?? jpg@cv.hp.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (3)
-
brauki＠cityweb.de -
jpg＠hpcvsjpg.cv.hp.com -
kyle＠binary.net