lpr: Unable to open temporary file

[Fairlight]

At Sat, Aug 13, 2005 at 11:36:36PM -0500 or thereabouts, 
suspect Tom Aldridge was observed uttering:
> Fedora Core 1. It's a box that's been in existence for going on two 
> years. It's been working fine. filePro printing has been fine all along, 
> until now. Obviously something has changed. I can print from the command 
> line as any user. PFTMP=/tmp. /tmp permissions are drwxrwxrwx (okay I'm 

ANY user?  Have you tried printing as the 'filepro' user specifically?

> sure that's wrong). Sorry, someone else setup the box, I just use it. 

And what did your illustrious admin say about the issue after having looked
at it carefully?  Did you even ask them?

And yes, /tmp should be 1777, not 0777.  But what you have will not cause
the problem.

> Other ideas?

Lots.

Anything from a slightly flaked out package, to a full filesystem, to a
cracked system that someone's having fun with.  Any one of many things
inbetween.  Impossible to say without seeing more details.  Need more data.
The best person to ask is the one that's been maintaining it for two years.
Assuming anyone's even touched it.  Sounds like it's had zero maintenance
if someone just set it up, and you just use it.

On a hunch, 'df' and see if any of the filesystems are full.  You mention
/tmp, but lpr and its associated subsystem won't care about /tmp.  It's
likely trying to use /var/spool which is probably on /var, and it appears
to be what's having problems, not filePro, despite the fact that only
filePro has issues.  Maybe you're printing tiny files that fit on a mostly
full filesystem when using the CLI, but printing huge reports from filePro.
Maybe the filesystem use is in a huge state of flux and you keep hitting
it at the wrong times.  Who knows?  You don't exactly delve into great
detail here.  Assuming nothing's corrupt, either it can't read the original
file, or it really has issues with the destination.  The latter could be
permissions, or it could be space.  There aren't a hell of a lot of options
inbetween.

Do you even know which print subsystem you have?  Given the vintage, it's
probably either LPRng or CUPS.  I doubt it's the old BSD-derived lpr/lpd
system.  I'd suggest verifying it with rpm once you find it, for starters.

Sounds like an OS issue, not a filePro issue, at any rate.  It may only
appear from filePro, but your error is definitely coming from lpr.  Ergo,
it's probably not filePro's fault.

m->