Iman Mayes on 4 Dec 2003 01:21:02 -0500 |
Thanks for the info. I *suspect* that the program I called was never executed because by moving it to another location I solved the problem (probably permissions or something). I think that it was the PHP system function that returned this code. Maybe PHP is not properly handling the error codes. The PHP docs say that system() will return any system errors that are generated on failure and a 0 for success. Iman On Wed, 2003-12-03 at 23:42, Walt Mankowski wrote: > On Tue, Dec 02, 2003 at 05:11:32PM -0500, Iman Mayes wrote: > > Does anyone know how to interpret the return codes from calling system() > > in PHP? I get 126 while trying to execute a command, but if I remember > > correctly that is not the *real* errno value. > > If it works like system(3), the return code looks like this: > > BITS MEANING > 0-6 signal which killed your child process > 7 did child process core dump? > 8-15 exit status of child process > > 126 still seems odd, though. It means you got a 0 return code, it > didn't dump code, and the child aborted with signal 126. However, > 126 isn't one of the standard signals. > > Strange... > > Walt -- Iman Mayes <imayes@verizon.net> ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|