Apache2 and FPCGI 2.0

[Fairlight]

Simon--er, no...it was John Sica--said:
> But the catch is that the apache2 user "daemon" cannot view the file 
> owned by filepro in 600 mode.  This permission error is in the apache 
> error log.

That's just basic unix permissions.  No surprises there.

> When "filepro" is the apache2 user, the htm file does not get populated, 
> and only when the apache2 user is "filepro" can the browser read the 
> file owned by filepro.

That part -is- a surprise.  I can only theorise that your fpcgi runs, maybe
even clerk or report, but clerk or report is crashing for some reason under
these conditions.

Have you tried appending a redirect like ">/tmp/cgierr.txt" to your
command, then looking at it with `less` to see if/where filepro is dying
before populating the field?

> Any ideas on how to modify apache2 to create a file with more liberal 
> permissions, or fpcgi2 to work when filepro is not the apache2 user?

Apache isn't creating the files.  Either fpcgi, clerk, or report is doing
that.  There's nothing to tune in apache with regards to creating files.
Nor is there anything to tune with regards to reading files, as that's
entirely based on unix file permissions.

Your problem is either fpcgi, clerk, or report.  You need to do debugging.
Best way to do that with your particular environment is redirect logging
and analysis.

Funny how I never have these problems with OneGate...  :)  </shameless_plug>

mark->
-- 
Audio panton, cogito singularis.