Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!brutus.cs.uiuc.edu!apple!motcsd!motsj1!mcdchg!chinet!john From: john@chinet.chi.il.us (John Mundt) Newsgroups: comp.unix.questions Subject: Re: Remote spooling; How do *you* submit files to a remote spooler? Message-ID: <1990Feb5.145342.19534@chinet.chi.il.us> Date: 5 Feb 90 14:53:42 GMT References: <855@pmday_2.Dayton.NCR.COM> Reply-To: john@chinet.chi.il.us (John Mundt) Organization: Chinet - Chicago Public Access UNIX Lines: 34 In article <855@pmday_2.Dayton.NCR.COM> steve@pmday_2.Dayton.NCR.COM (Steve Bridges) writes: >In article larry@focsys.uucp (Larry Williamson) writes: >> >> text deleted about remote spooling...... > >We had a similiar problem here. We are using Expanded Towernet (a >version of Xerox's XNS) to go between Towers. One unfortunate problem >is that the version of Towernet for our 32/800 supports remote >printing to either an lpr printer or lp printer on any machine on >the network through either nprint or lprint. I took an even lazier approach. For each remote printer I wanted to have people use, I created a dummy printer on the local machine. Then, I set up the actual printing script (in /usr/spool/lp/admins/lp/interfaces on SysV3.2) and basically changed the line that actually cats the file to the printer device with for file in "$files" do cat $file | uux -n - "${DEST_MACHINE}!lp $REMOTE_PRINTER_NAME -s" done You can do a lot of fancy stuff within the interfaces scripts, since the print spooler really doesn't care what happens to the file once it is shipped off to the script. If you haven't done this often, use the "dumb" printer model and go to work on it. You could even have the file compressed and uncompressed at the other end if large files get printed. -- --------------------- John Mundt Teachers' Aide, Inc. P.O. Box 1666 Highland Park, IL john@admctr.chi.il.us *OR* fred@teacha.chi.il.us (312) 998-5007 (Day voice) || -432-8860 (Answer Mach) && -432-5386 Modem