Thanks, Rob and Loren. Rob appears to be correct, I see my shopsite URLs
include cgi-sys/cgiwrap so looks like they use cgiwrap, not suExec. Either
way, the Order API runs my script as me, not nobody.
I notice my log file created by my script is actually owner "nobody", group
"users" so if I set directory and file mask to 775 instead of 755 that
should allow both me and nobody to write it.
--
David P. Gray
Gray Design Associates
"Loren" <loren_d_c@yahoo.com> wrote in message
news:e7u1uj$k0f$1@eval.shopsite.com...
Pair is running the ShopSite cgi's through a program called 'suexec'
which changes the user the cgi's are run as to your own account user.
Since that is the user the ShopSite thankyou.cgi is run as, that will be
the same user that any child process (i.e. your custom php script) is
run as, too.
In general, I would say that if your Order API custom cgi is the same
ownership and permissions as the working thankyou.cgi, then it should
work too (at least as far as execute permissions go).
-Loren
David Gray wrote:
Thanks for the reply, Rob. I'm not sure if that is correct in my case
though. To test it I put a call to /usr/bin/id in the php script and
these
are the results I got:
php run via browser: uid=65534(nobody) gid=998(www) groups=998(www)
php run via Order API: uid=3062(dgray) gid=1000(users)
groups=1000(users)
The last one is the same one I get if I run "id" from the command line.
Is
this something I should take up with my ISP (pair.com)?