Process tracking with mod_fcgid is not the same as with suPHP

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • iseletsk
    replied
    NM, I see what you mean, you can see script name being executed when using mod_fcgid, as same binary is executed for multiple scripts.

    Leave a comment:


  • xvidvideo
    replied
    I have made some tests and find out that the:

    ps auxww

    command does not display the full path to a php process like suPHP does.

    Leave a comment:


  • xvidvideo
    replied
    Thank you Igor,

    The /usr/bin/php path was just an example.

    Ill try if ps auxww will get me the full process path.

    Thanks.

    Leave a comment:


  • iseletsk
    replied
    ps auxww will get you full path
    but it is /usr/bin/php that is running for the customer, it just that for each customer /usr/bin/php might be different php binary (either 5.3 or 5.4, etc...)

    Leave a comment:


  • xvidvideo
    replied
    Hello all,

    Does someone know is it possible to see the full process path when using mod_fcgid?
    When running suPHP and run: top -c the processes are shown similar to this:

    /usr/bin/php /home/username/public_html/script.php

    meaning: the full path to the process is shown.

    When running mod_fcgid I only get this:

    /usr/bin/php

    Is there something I can do to see the processes in suPHP style?

    Regards.

    Leave a comment:


  • Process tracking with mod_fcgid is not the same as with suPHP

    Full path to the process is not shown when using mod_fcgid
Working...