bug in viewprt?

Jay R. Ashworth jra at baylink.com
Wed May 12 11:13:07 PDT 2004


On Wed, May 12, 2004 at 02:20:46PM -0400, Bob Stockler wrote:
> On Wed, May 12, 2004 at 12:52:31PM -0400, Jay R. Ashworth wrote:
> | I believe I've discovered a design deficiency in viewprt.
> | 
> | Apparently, in certain circumstances, filepro creates -p output files
> | which are not readable by the general public.  For some reason, while
> | the less command spawned by viewprt can read them (it apparently
> | inherits viewprt's EUID), lp pukes because it cannot (a permission
> | error).  I believe this is because it's the lp *unspooler* program,
> | which runs as user lp, that tries to open said file.  I saw two
> | possible solutions: chmod the temp file inside viewprt, or modify
> | 
> | lp -n $print $dir/$file
> | 
> | into
> | 
> | cat $dir/$file | lp -n $print
> 
> Useless use of "cat" #50,999,999.  Replace with:
> 
>    <$dir/$file lp -n $print

Some shells won't interpret variables as the argument of a redirection
(specifically, older SCO shells), and in any event, put the redirection
on the *right*, Bob.  :-)

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Member of the Technical Staff     Baylink                             RFC 2100
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 647 1274

        "They had engineers in my day, too."  -- Perry Vance Nelson


More information about the Filepro-list mailing list