Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!dayton!umn-cs!wsmith
From: wsmith@umn-cs.UUCP
Newsgroups: comp.dcom.lans
Subject: Re: Connecting a printer to an Ethernet
Message-ID: <57700001@umn-cs.UUCP>
Date: Wed, 11-Mar-87 20:35:00 EST
Article-I.D.: umn-cs.57700001
Posted: Wed Mar 11 20:35:00 1987
Date-Received: Fri, 13-Mar-87 05:18:09 EST
References: <5923@charlie.UUCP>
Lines: 30
Nf-ID: #R:charlie:-592300:umn-cs:57700001:000:1214
Nf-From: umn-cs!wsmith    Mar 11 19:35:00 1987



Assuming you are using printcap with a :rm=bridge: or some such thing,
the problem is that this causes your Gould to look for a print daemon
to send the file to on the Bridge box (which isn't running such a thing).

There is no need to change the line printer daemon.  What you need to do
is set up a printcap entry as below:

bridge|lp2:\
	:lp=/dev/null:sd=/usr/spool/bridge-lp:lf=/usr/adm/bridge-errs:\
	:af=/usr/adm/bridge-acct:if=/usr/local/bin/bridge-filter:tr=\f:

(Make sure the files are writeable by daemon, otherwise the daemon may
go into an infinite loop trying to write them).

Next you write the program /usr/local/bin/bridge-filter to prepend a banner 
to the output (there may be an easier way) - the arguments lpd sends to
this program are $5=user, $7=host (for the others, see its documentation).
Then you have this program start a "telnet" session to the bridge
box and send the banner and file along.  Bridges only speak telnet,
so you must use that (assuming you are using the TCP software, not the
XNS stuff).

I've never done this exact application, but I have used a similar setup
for remote printing to non-BSD machines.  Good Luck!

Randy Smith
wsmith@umn-cs.arpa
..!ihnp4!umn-cs!wsmith