On Tuesday 15 August 2006 09:38, Brad Bonkoski wrote:
> Stut wrote:
> > Brad Bonkoski wrote:
> >> Had this problem in the past, and always programmed around it, but
> >> wondering if there is an easier way.
> >>
> >> Good Example:
> >> Creating a setup for connecting to a mysql database. Want to do
> >> something simple to make sure they have entered a valid
> >> username/password for the database.
> >> So, the idea is something like:
> >> $rc = exec("mysql -u $user -p{$pass}", $output);
> >> The problem is one error, the stderr does not go to the output array,
> >> but rather to the screen.
> >>
> >> Previously I would redirect the stderr to a file, and then evaluate
> >> the contents of the file, but is there an easier way to get this into
> >> the PHP variable with no risk of having the output make it through to
> >> the screen?
> >
> > I may be missing something, but why in the name of all that is holy
> > would you want to shell out to try connecting to mysql? Why not use
> > mysql_connect and avoid the potentially massive security hole you're
> > building?
> >
> > -Stut
>
> Perhaps poor illustration of the question...the question being how to
> issue system like commands in PHP which would allow you to trap not only
> stdout, but also stderr.
> -Brad
Best example I found was:
$shell_return = shell_exec($shell_command." 2>&1");
that should redirect stderr to stdout and thus you'd get both.
--
Ray Hauge
Programmer/Systems Administrator
American Student Loan Services
www.americanstudentloan.com
1.800.575.1099
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
