DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42580>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42580


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




------- Additional Comments From [EMAIL PROTECTED]  2007-06-16 15:28 -------
(In reply to comment #5)

> The apr problem only occurs, when the Apache runs in a Solaris Zone. When it
> runs in the global context (means: not in a zone), the apache restart does NOT
> cause an APR_TIMEUP.

This is an interesting information.

> 
> Is it right, that the error is from srclib/apr/poll/unix/poll.c from line 253?

As you are using zones I suppose that you are running on Solaris 10. So I guess
that you have port support there and you should be rather in line 291 of port.c
in the same directory. You can check if you have port support by checking if
HAVE_PORT_CREATE is defined in srclib/apr/include/arch/unix/apr_private.h

> And the causing function is the poll(..) system call?

I think it is rather port_getn.

> 
> "man poll" under Solaris says the same as the source code:
> 
> RETURN VALUES
>      Upon  successful  completion,  a   non-negative   value   is
>      returned.  A  positive  value  indicates the total number of
>      file descriptors that  has  been  selected  (that  is,  file
>      descriptors  for  which  the  revents member is non-zero). A
>      value of 0 indicates that the call timed  out  and  no  file
>      descriptors have been selected. Upon failure, -1 is returned
>      and errno is set to indicate the error.
> 
> 
> Perhaps its not possible to execute poll(..) in a Solaris zone?
> Or there is a missing device in /dev/?

I don't think that this is the case. If you wouldn't be able to use this system
call httpd would not work at all. I suppose that it has something to do with the
restart logic itself. What happens (error message wise) if you

1. Stop httpd
2. do a gracefull restart
3. do a graceful shutdown

in your zone.


> 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to