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