getting dumped out when settting print file

[Fairlight]

On Fri, Jun 23, 2006 at 06:19:01PM -0500, Richard D. Williams may or may
not have proven themselves an utter git by pronouncing:
> OS - RH Enterprise

Which one?  3?  4?  Earlier?

> I have a processing table (750 lines) than simply sets a printer file; i.e.
> printer file (f), where f is equal to /tmp/duedil15714.
> 
> When this line is executed the program dumps me out.
> I can run this from the command line, with debug on and this is the error.
> 
> Enter Command > sh: /tmp/duedil15714: No such file or directory
>                                                                sh: 
> /tmp/duedil15
> 714: No such file or directory
>                               [root at mail richardw]#

1) Show the actual processing lines.  Your description is entirely
inadequate for the purposes of this discussion when coupled with your
results.

2) Why are you doing this as root?  There's no need to be in as root for
what you're doing.  Given the steps you're taking (seemingly randomly) to
try and "solve" the problem, I'd say it's potentially dangerous.

3) DNOENT (no such file or directory) means just that.  It's unambiguous;
the file isn't there.  Given actual code, we can probably find out why
you're getting what you're getting.

> I have switch to different PFCONFIGs, I have changed directories, I have 
> made sure the perms. are set to 777, owner filepro, group filepro. etc 
> etc etc.

I'm 100% sure that making your files needlessly insecure will not solve
the problem.  The change you're making is inconsistent with the error
reported.  I'm reasonably confident that changing random variables out
of desperation without knowing why you're doing so will only confuse the
matter and make it needlessly harder to track down.

> But, it works fine with rclerk!

That much I find odd, although such inconsistencies are not unprecedented.

> What's up with that?

If you'd post the code snippet instead of a vague description of it,
maybe we could tell you.  At this exact moment, all I can tell you
that the file isn't there at the point the shell reports this fact.
As I said, DNOENT is unambiguous I have no way of knowing if that's
coming from SYSTEM, a separate shell script called from SYSTEM, both,
etcetcetcetcetcetcetcetcetc.  Obviously sh is involved in the chain, but
the context is unclear.  If you're calling a shell script, include that as
well, please.

mark->