Posted by Aaron Saray on 11/29/07 12:13

On Nov 28, 5:37 am, Erwin Moller
<Since_humans_read_this_I_am_spammed_too_m...@spamyourself.com> wrote:
> JahMic wrote:
> >>> application is in the same directory as the scripts. If I change
> >>> $MaskData = "mask.exe -e \"TestString\""; to $MaskData = "./mask.exe -
> >>> e \"TestString\""; (the addition of ./) the value of $ReturnValue is 1
> >>> and no values for $Result and $output. (Output should be a long
> >>> string).
> >> Ok, the $ReturnValue says 1, so I expect that the command DID run
> >> succesfully.
>
> > Actually, on successful systems $ReturnValue is 0.
>
> Oops. Sorry for the confusion.
>
>
>
> >> Very strange your $Output array is empty.
>
> > Is there a possible way to pipe or redirect the output?
>
> Well, passthru() should do this.
>
> <quote>
> The passthru() function is similar to the exec() function in that it
> executes a command . This function should be used in place of exec() or
> system() when the output from the Unix command is binary data which
> needs to be passed directly back to the browser. A common use for this
> is to execute something like the pbmplus utilities that can output an
> image stream directly. By setting the Content-type to image/gif and then
> calling a pbmplus program to output a gif, you can create PHP scripts
> that output images directly.
> </quote>
>
>
>
> >> Of course, what you want now is run the command by hand in a shell as
> >> user PHP, being on Apache: Apache, or nobody or www-data, or
> >> IUSR_<machinename> on IIS.
>
> >> But you cannot.
>
> >> So you'll have to debug by guessing.
> >> Does the mask.exe has execution rights for PHP-user?
>
> > I've tried 777 to no avail.
>
> clear.
>
>
>
> >> Do you maybe use files in mask.exe that are not accecible by PHP?
>
> > No other files
>
> Anything else that might need additional rights?
> Maybe opening ports under 1024 on *nix?
>
>
>
> >> Throw in a full path to mask.exe instead of ./
>
> > to no avail?
>
> :-(
>
>
>
> >> Check your slashes, etc.
> >> Try passthru() instead of exec().
>
> > nada
>
> >> And last but not least, insult the supportdepartment of your hosting
> >> provider. ;-)
>
> > Don't worry about that, I'm giving them their due share of grieve.
>
> Sorry James,
>
> What you really need to do first is run the program from commandline to
> see if it actually works.
>
> You don't know for sure the program works. Is that right?
>
> But I understand that is not possible, since you don't have shell. :-/
>
> I think I would try the supportdepartment and ask then to try it for you.
> Give them the command and ask them to run it for you.
> If they refuse, shoot them. :P
>
> It is very difficult to debug like this of course.
> Sorry, I am also out of options.
>
> Good luck!
>
> Regards,
> Erwin Moller
>
> > Thanks, James
>
> >> Good luck.
>
> >> Regards,
> >> Erwin Moller
>
> >>> A hosting provider switch is likely, but this is an immediate issue
> >>> that I need to get taken care. Once again, any help is much
> >>> appreciated.
> >>> Thanks, J- Hide quoted text -
> >> - Show quoted text -- Hide quoted text -
>
> >> - Show quoted text -

What if you tried using exec to run the command but piping standard
out to one file and standard error to another file. Make sure both of
these files are in your home directory - and then use fopen to read
them. This probably won't help tooooo much but it might give you some
insight. Good luck!

[Back to original message]