Frederic Belleudy wrote: > Well I think I've found the answer: > the configure command is (in part): > > '--disable-cli' '--disable-pear' > > Ive got another server who is running fork script and '--enable-cli' is > in the configure command. then that is probably what the problem is - although I find it a strange compile option would have that effect. if you run ./configure --help you'll see the following: --disable-cli Disable building CLI version of PHP which doesn't suggest that it would have any effect on the workings of a webserver SAPI. > > Well Ill let you know guys if it works after I've recompiled apache try recompiling php - recompiling apache won't have an effect as far as that compile option goes. > How comes it does work when Im executing it from the shell and not from > the web??? > Any explanations? > > Frederic Belleudy wrote: >> Hello there, I hope someone resolved the same issue. I upgraded my >> server to 5.2.1 >> I got some script that are running background script (generally we >> call this technic FORKING) >> Ive got a web interface that running (depending the action chosen) >> other scripts in the background. >> My issue is, it doesn't work anymore since my new upgrade. >> So I'm using this line to run my background script from the web >> browser interface: >> /usr/local/bin/php test.php 2>&1 error.log >> >> if Im executing my script from the shell, my fork is working very >> fine! (Odd isn't it) >> I taught it could be owner and rights problems but it's not the case... >> >> Anyone got suggestions?? >> > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
