{"id":55220,"date":"2022-03-25T03:01:40","date_gmt":"2022-03-24T17:01:40","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=55220"},"modified":"2022-03-24T15:12:34","modified_gmt":"2022-03-24T05:12:34","slug":"php-shell_exec-versus-exec-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/php-shell_exec-versus-exec-tutorial\/","title":{"rendered":"PHP shell_exec Versus exec Tutorial"},"content":{"rendered":"
\"PHP<\/a>

PHP shell_exec Versus exec Tutorial<\/p><\/div>\n

Being suckers for “out of the box” solutions to programming issues, what comes “out of the box” with your (perhaps underlying) operating system of use is always inflicting “sucker punches” onto areas we didn’t know existed before … well, you had to be there, didn’t you?<\/font><\/p>\n

That’s why we really like PHP’s “exec”<\/a> and “passthru”<\/a> that we have used quite a bit in the past, to get through to that underlying operating system set of commands in its command line environment, as applicable. Even mobile platforms get a go here, because PHP is a serverside language addressing the RJM Programming linux web server, though you can download s_e.php<\/a> to your local (client) environment, and access a different perspective in an Apache\/PHP\/MySql local web server environment such as MAMP<\/a> to work in.<\/p>\n

Today, we compare “shell_exec”<\/a> to “exec” with our proof of concept PHP web application<\/a> we’ve written for you to try today, for you to see that “shell_exec” is everything “exec” is plus returning the entire command line command’s output, as distinct from the “just last line return” of exec …<\/p>\n