Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!dialogic!drich From: drich@dialogic.UUCP (Dan Rich) Newsgroups: comp.unix.i386 Subject: Re: uucp with tcp on 386/ix vers 2.0.2 Keywords: uucp tcp 386/ix Message-ID: <966@dialogic.UUCP> Date: 6 Oct 89 16:18:04 GMT References: <255@cipher.UUCP> <182@inpnms.UUCP> Reply-To: drich@dialogic.UUCP (Dan Rich) Organization: Dialogic Corp., Parsippany, NJ Lines: 34 In article <182@inpnms.UUCP> logan@inpnms.UUCP (James Logan) writes: >In article <255@cipher.UUCP> russ@cipher.UUCP (Russ Harvey) writes: ># Hi, we have 5 ISC 386/ix version 2.0.2 machines ># connected via ethernet (WD8003E, ISC's TCP/IP), ># and want to do something natural like have ># the ability to print files on all machines, ># even though there is only one printer (HP LaserJet II). > >What's wrong with the rshl(1) command? If you are on machine "A" >and the printer is on machine "Z", just use: > > rshl Z lp > This will only work if you give all of your users accounts on the machine with the printer, and if all of them have a .rhosts file. I find that a little too much to expect of most users :-). Also, I have removed the .rhosts file from root (I don't want people to be logging, or rshl'ing into our fileserver as root), so now I can't print from remote machines as root. If you are running rfs, a better solution might be (this just came to mind, and I haven't tried it yet, so don't yell if it doesn't work) to create a remote device directory. Then, place links to all of the devices you want to be able to access remotely in this directory. You should then be able to define a printer to use the remote device, instead of the usual local device. We already use this for our tape drive, so I don't see any reason why it wouldn't work for a printer. -- - Dan Rich | | Dialogic Corporation drich@dialogic.UUCP | - Time is an illusion. | 300 Littleton Rd or | Lunchtime, doubly so. - | Parsippany, NJ 07054 uunet!dialogic!drich | - Douglas Adams | (201)334-8450 x213