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