tags:

views:

469

answers:

4

I have a number of command line scripts in PHP that use exec() to perform tasks such as restarting services, loading MySQL timezone files, etc. While exec() itself does not output anything to the screen, some of the commands I am running are forcing output that I can't seem to suppress (even with ob_start()/ob_end_clean()). For example, the following would load timezone files into MySQL. We run this periodically to make sure MySQLs timezone data is up to date:

 $command = 'mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql mysql';
 exec($command, $output, $result);

In this example, I would expect all output from the command to be written into $output, but I still get the following output forced to the screen:

Warning: Unable to load '/usr/share/zoneinfo/Asia/Riyadh87' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/Asia/Riyadh88' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/Asia/Riyadh89' as time zone. Skipping it.
...

Is there any way to suppress this output? Redirecting to /dev/null is not ideal as that would cause PHP to continue processing without waiting for the command to complete.

Thanks in advance,
~ JamesArmes

+2  A: 

Redirecting stderr alone should not influence where processing takes place, just make sure not to add an &. It should only run in the background if you redirect the output and make it run in the background.

Edit:

Cracked open cygwin, you need to redirect stderr for the first command, give this a try:

$command = 'mysql_tzinfo_to_sql /usr/share/zoneinfo 2> /dev/null | mysql mysql';
exec($command, $output, $result);
Yannick M.
Ben James
Hmm indeed, that seems more plausible. I will correct my answer
Yannick M.
Redirecting using $command = 'mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql mysql 2> /dev/null';still causes the same output. However, calling my script like php mysql_timezones.php 2> /dev/nullproperly suppress the output. Is it possible to get the same results without calling my script in that fashion?
JamesArmes
Yannick M.
Still no difference
JamesArmes
I have altered my response
Yannick M.
I just figured this out and came here to post my findings, only to find that you beat me to it :-P It was indeed mysql_tzinfo_to_sql outputting the errors and not mysql. Thanks to everyone who responded!
JamesArmes
+1  A: 

Just redirect stderr to /dev/null

$command = 'mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql mysql 2>/dev/null';

or to stdout

$command = 'mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql mysql 2>&1';
jitter
+1  A: 

Redirecting to /dev/null does not cause PHP to stop waiting for the command. Adding a & does do this, you probably associate the two because the final & is often used in conjunction with a redirect.

In response to Yannick's (deleted) comment: it seems if you want to run something in the background in PHP, you must redirect as well as using &. This does not mean that redirection alone causes it to run in the background.

Ben James
JamesArmes
JamesArmes: that is precisely what the 2nd part of my answer was intended to explain
Ben James
A: 

According to http://us3.php.net/manual/en/function.shell-exec.php you can assign this command's output to a variable.

You don't necessarily have to do anything with the variable, which means you are effectively suppressing output.

Hope that helps!

iddqd
That's what the $output variable in the exec() call is supposed to do (it's passed by reference). I have tried using shell_exec() and it produces the same results.
JamesArmes