kowalski@svax.cs.cornell.edu (Jeffrey Kowalski) (12/07/89)
Is is possible to remote print to a SYSV printer from a BSD printer? My BSD printcap is something like foo|Foo Printer on the Iris:\ lp=:rm=butternut:rp=decwr1: butternut is a Silicon Graphics Iris 4D running SYSV. It's got a printer that's named (over there) "decwr1" as shown by a 'lpstat -p' I've modified the /etc/hosts.equiv on butternut to include my BSD machine (acacia) that's got the virtual printer foo. After an "lpr -Pfoo junk.txt", a "lpq -Pfoo" gives ]connection to butternut is down ] ]acacia: waiting for butternut to come up ]Rank Owner Job Files Total Size ]1st jeff 0 junk.txt 5511 bytes So, there you have it. What gives? You may email replies to jeff@acacia.cadif.cornell.edu, or to the the reply line. Thanks, jeff (signatures are for the insecure)
mitch@hq.af.mil (Mitchell..Wright) (12/07/89)
kowalski@svax.cs.cornell.edu (Jeffrey Kowalski) writes: >Is is possible to remote print to a SYSV printer from a BSD printer? > [ ... ] >]connection to butternut is down >] >]acacia: waiting for butternut to come up >]Rank Owner Job Files Total Size >]1st jeff 0 junk.txt 5511 bytes > >So, there you have it. What gives? > The problem is that the System V machine does not have lpd running. It probably doesn't have it at all. To allow such remote printing, there are a few things that you can do... 1) Write a simple version of lpd for the System V machine. 2) Port an lp[dr] to your SV machine. PLP is in the Public Domain. 3) utilize the filters in printcap to execute a script that would rsh <host> lp <options> <file> in one form or another. This method works fine as a quick hack, but I do not recommend it to be used in a production environment. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Mitch Wright Currently under contract to: I-NET, Inc. USAF 7th CG, The Pentagon ARPA: mitch@hq.af.mil gretzky@unison.larc.nasa.gov UUCP: uunet!hq.af.mil!mitch AT&T: (202) 696-6070 (202) 696-6030 (FAX) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
mfuller@prandtl.nas.nasa.gov (Mike J. Fuller) (12/08/89)
In article <MITCH.89Dec7102805@hq.af.mil> mitch@hq.af.mil (Mitchell..Wright) writes: >kowalski@svax.cs.cornell.edu (Jeffrey Kowalski) writes: > >>Is is possible to remote print to a SYSV printer from a BSD printer? >> [ ... ] >The problem is that the System V machine does not have lpd running. It >probably doesn't have it at all. To allow such remote printing, there are a >few things that you can do... [ ... ] This is what I did: get the source to the BSD lpr facilities from somewhere like uunet.uu.net and apply the patches that were posted to the network a while ago to get it to run on SysV. To access a printer called "foo" on a SysV machine called "bar", use a printcap entry like: foo:\ :lp=:rm=bar:rp=foo:sd=/usr/spool/foo:\ :lf=/usr/spool/foo/foo-errs:mx#0:rs: And on the SysV machine, assuming that you installed the BSD lpr facilities and also have lp working correctly: foo:\ :lp=/dev/null:sd=/usr/spool/foo:\ :of=/usr/bin/lp:lf=/usr/spool/foo/foo-errs:\ :mx#0:rs:sb:sf:sh: This is necessary because the patches (at least the ones I got) are really only intended to allow your SysV machine to print to BSD machines. ie., it cannot actually print to a printer attached to a serial port. However, if lp is working correctly, you can just pass the file to lp and let lp deal with it. Yeh, I admit that it's a kludge, but I have abused the output filter field much worse than that. I have one output filter that is a script that copies the file to the default decnet account on a vax running VMS and issues a remote command to print it and delete it. I know one machine where they use a similar method to access MVS printers. /-----------------------------------------------------------------------------\ | Mike J. Fuller |Internet: mikef@sarah.lerc.nasa.gov |You'd be paranoid, | |----------------| mikef@zippysun.math.uakron.edu|too, if everyone | |/\/\/\/\/\/\/\/\|Bitnet: r3mjf1@akronvm |was out to get you!| \-----------------------------------------------------------------------------/
daveh@xtenk.sgi.com (David A Higgen) (12/12/89)
In article <MITCH.89Dec7102805@hq.af.mil>, mitch@hq.af.mil (Mitchell..Wright) writes: > kowalski@svax.cs.cornell.edu (Jeffrey Kowalski) writes: > > >Is is possible to remote print to a SYSV printer from a BSD printer? > > [ ... ] > >]connection to butternut is down > >] > >]acacia: waiting for butternut to come up > >]Rank Owner Job Files Total Size > >]1st jeff 0 junk.txt 5511 bytes > > > >So, there you have it. What gives? > > > The problem is that the System V machine does not have lpd running. It > probably doesn't have it at all. To allow such remote printing, there are a > few things that you can do... > > 1) Write a simple version of lpd for the System V machine. > 2) Port an lp[dr] to your SV machine. PLP is in the Public Domain. lpr/lpd will be available as an optional alternate printer management system for SGI machines in the next (3.3) release, coming in a couple of months. Dave Higgen