ID: 19835 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Bogus Bug Type: Unknown/Other Function Operating System: Unix (OpenBSD-3.0) PHP Version: 4.2.3 New Comment:
Each user has it's own limit, when you logged in on a different terminal was it under the same user as the one executing the shell scripts? Previous Comments: ------------------------------------------------------------------------ [2002-10-09 14:42:31] [EMAIL PROTECTED] No, the system did not reach the user limit, i could log in and spawn more processes. It was related to PHP ! I searched in google and saw a preceding bug similar to this one that was due to "a misbehaviour in exec()". ------------------------------------------------------------------------ [2002-10-09 14:09:12] [EMAIL PROTECTED] Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Thank you for your interest in PHP. This usually means that the system has reached maximum allowed user process' and cannot start any new ones. You can view the limit via the 'ulimit -a' command. ------------------------------------------------------------------------ [2002-10-09 13:54:51] [EMAIL PROTECTED] Lately, we figured out that PHP was having problems sometimes while working with exec(). We would get a 'Warning: could not fork [some/scripts.sh]' for a delay of about 10 minutes, after what everything comes back to normal. I tried to log into the server while PHP was giving me the error and noticed that everything was working fine. This happened once with 4.2.2 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=19835&edit=1
