Not what I meant, just login into the server from the console or terminal, using the apache account for testing to see if the command line work. That's all. If it work then it meant it will work on PHP and that the apache file permission or ownership is not the issue. Also, it meant you do not need to write PHP coding to login to access or execute those scripts. That way, you move on and find out what else is causing the problem. Well, when Apache is compiled, the Apache account is created and the account is never created without a username and password.
"Curt Zirzow" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > * Thus wrote Scott Fletcher ([EMAIL PROTECTED]): > > What you will need to do is to login using the Apache account from the > > terminal login and execute the command line code. If it doesn't work then > > you know the problem had nothing to do with Apache and PHP. > > The apache account shouldn't have a username and password, for > security reasons, so an su to the apache account would be a way to > login as the user: > > # su <apacheaccount> > > Curt > -- > "I used to think I was indecisive, but now I'm not so sure." -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
