Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!princeton!jonlab!jon
From: jon@jonlab.UUCP (Jon H. LaBadie)
Newsgroups: comp.sys.att
Subject: Re: Printing through UUCP
Summary: you may need to copy the files
Keywords: 3B2, UUCP, Printing
Message-ID: <897@jonlab.UUCP>
Date: 19 Dec 90 13:44:34 GMT
References: <1990Dec10.164131.5403@DMI.USherb.CA> <131@dlss2.UUCP> <1868@fallst.UUCP>
Organization: 4455 Province Line Rd., Princeton, NJ 08540
Lines: 26

In article <1868@fallst.UUCP>, tkevans@fallst.UUCP (Tim Evans) writes:
> In <18809@netcom.UUCP> cmilono@netcom.UUCP (Carlo Milono) writes:
> 
> >I have implemented this using UUX commands; below is a sample command
> >which can be included in a standard lp/interfaces script, as appropriate.
> 
> >uux "remote!lp !myfile1"  [this would print myfile on a printer on remote]
> 
> You must also "authorize" the 'lp' command to be executed via uux.

On some versions of UNIX in which I have done this, the data files were
removed as soon as the remote lp command was executed.  However, the
printing via lpsched occurred at some later time and had no data files
to print.

Thus, it was necessary to either write a customized shell script to
copy the data files to a safe location (then administrative cleanup
was required), pass the files to lp via standard in ("lp < data"),
or use the copy option ("-c") of lp to force it to make private
copies of the data that it automatically deletes upon printing.

Jon

-- 
Jon LaBadie
{att, princeton, bcr, attmail!auxnj}!jonlab!jon