> of the n children which can serve requests, n-1 would have the truss
> you show (nothing at all wrong) and the remaining one (the one that
> has obtained the AcceptMutex on which the others await) has the
> interesting backtrace and truss
The next hangup will come, I'm sure of that. When it does
2010/6/2 Igor Galić
> >
> > >r...@atvt1uajas001:~# truss -f -p 26794
> > >26794: fcntl(54, F_SETLKW64, 0xFF1E17C0) (sleeping...)
> >
> > This is consistent with, but not sufficient to be certain of, the
> > problem I alluded to. You'd need to look at the truss of child
> > processes not blocked
> > Unless you have a support subscription for that product, build the
> > latest httpd and php yourself from source. (Yeah, you'll probably
> > need to build some add'l support libraries too, but OTOH it is just
> a
> > matter of time until you get tired of 2.2.11 and 5.2.9-ish.
I believe that
On Wed, Jun 2, 2010 at 10:17 AM, Jeff Trawick wrote:
> 2010/6/2 Igor Galić :
>>
>> Hello happy people.
>>
>> I'm experiencing certain troubles with httpd (provided by WebStack 1.5) on
>> Solaris 10
>
> Unless you have a support subscription for that product, build the
> latest httpd and php yours
2010/6/2 Igor Galić :
>
> Hello happy people.
>
> I'm experiencing certain troubles with httpd (provided by WebStack 1.5) on
> Solaris 10
Unless you have a support subscription for that product, build the
latest httpd and php yourself from source. (Yeah, you'll probably
need to build some add'l
Hello happy people.
I'm experiencing certain troubles with httpd (provided by WebStack 1.5) on
Solaris 10
After a network hickup (I suspect) httpd refuses to answer.
The Process lingers in a state of waiting for the network interface, see the
truss below.
It doesn't recover from this state unt
