ID:               24189
 User updated by:  anton at valuehost dot ru
 Reported By:      anton at valuehost dot ru
-Status:           Bogus
+Status:           Closed
 Bug Type:         Sockets related
 Operating System: FreeBSD 4.8
 PHP Version:      4.3.2
 New Comment:

Do not want to help well and it is not necessary, in backtrace I and
itself can understand.


Previous Comments:
------------------------------------------------------------------------

[2003-06-15 10:58:08] [EMAIL PROTECTED]

Not enough information -> bogus. (get rid of the zendoptimizer on some
machine and provide a backtrace, otherwise -> not bug)


------------------------------------------------------------------------

[2003-06-15 10:55:20] anton at valuehost dot ru

In it that all and the problem, on dev server to us was not possible to
receive this mistake.
The problem arises on production a level what from scripts of users of
her causes to understand not really, we hold over 25000 sites.

We at once find out any mistakes and we celebrate them quickly enough,
and this of us has led up a blind alley :(

But I can tell precisely, that all functions which work with socket
cease to work, what that restriction on work mod_php is imposed.

------------------------------------------------------------------------

[2003-06-15 10:25:52] [EMAIL PROTECTED]

You should have a dev machine to test this on.
Just leave ZendOptimizer out. If you can't do this and can't provide
decent backtrace, we can't fix anything.


------------------------------------------------------------------------

[2003-06-15 07:49:27] anton at valuehost dot ru

It is impossible to switch off ZendOptimazer, on servers is from 500 up
to 1500 sites, the some people use Zend if we shall switch off it at us
there will be problems.

Let's think as it is possible to make it without deenergizing, can be
ktrace will approach?

------------------------------------------------------------------------

[2003-06-15 07:45:46] anton at valuehost dot ru

if to make "apachectl restart" the problem will disappear for some
time, but after a while it proves again while it was necessary to make
restart on cron each 4 hours.
And the problem does not disappear if to do "killall -HUP httpd".

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/24189

-- 
Edit this bug report at http://bugs.php.net/?id=24189&edit=1

Reply via email to