Greetings All,
Had a need to build a local copy of Apache 1.3.33 (source) and after
setting the env vars as described for NetWare, got the following:
Unable to locate winsock2.h
A search found this in \Novell\ws295sdk\include, so I added that to the
Include path list (solved that), but now get
Lese selbst:
http://www.npd.de/npd_info/deutschland/2005/d0405-13.html
Neue Dokumente:
http://www.rp-online.de/public/article/nachrichten/politik/deutschland/87647
Botschafter in Kiew beschwerte sich noch 2004:
http://www.rp-online.de/public/article/nachrichten/politik/deutschland/85735
Apache keeps the read handle to the pipe open in the child process.
Thus, if the piped logger goes away and a new piped logger doesn't
inherit the same handles, a child process can hang writing to the
logger since the child process itself is keeping the read side of the
pipe open.
The scenario
Andr Malo wrote:
Once forked off, 2.1.x would be *stabilizing* branch, that finally leads
to a 2.2.x branch, when we feel, it's stable (svn mv 2.1.x 2.2.x?). From the
2.1.x branch we tag alpha and beta releases; from *stable* 2.2.x rc and
stable release. I think that's exactly the point of the
On Sun, May 15, 2005 at 09:22:57AM -0400, Jeff Trawick wrote:
...
Joe Orton says, To fix this properly, I suppose piped loggers should not get
SIGTERMedduring a graceful restart, they should read till EOF then
exit(0): then
when the last child attached to the piped logger for a particular
Perhaps while we're dealing with piped log process/pipe management
perhaps we can take care of this one at the same time:
http://issues.apache.org/bugzilla/show_bug.cgi?id=34537
Thanks!
Tom
Jeff Trawick wrote:
Apache keeps the read handle to the pipe open in the child process.
Thus, if the
Full Article:
http://service.spiegel.de/cache/international/0,1518,345889,00.html
Lese selbst:
http://www.heise.de/newsticker/meldung/59427
On 5/15/05, Tom Hoefakker [EMAIL PROTECTED] wrote:
Perhaps while we're dealing with piped log process/pipe management
perhaps we can take care of this one at the same time:
http://issues.apache.org/bugzilla/show_bug.cgi?id=34537
My own rationalization for current behavior (admittedly weak):
On 5/15/05, Joe Orton [EMAIL PROTECTED] wrote:
On Sun, May 15, 2005 at 09:22:57AM -0400, Jeff Trawick wrote:
...
Joe Orton says, To fix this properly, I suppose piped loggers should not
get
SIGTERMedduring a graceful restart, they should read till EOF then
exit(0): then
when the last
On 5/15/05, Jeff Trawick [EMAIL PROTECTED] wrote:
Apache keeps the read handle to the pipe open in the child process.
Thus, if the piped logger goes away and a new piped logger doesn't
inherit the same handles, a child process can hang writing to the
logger since the child process itself is
good point. I suspected there was a reason for the difference in
behavior between this and mod_log_config.
Jeff Trawick wrote:
On 5/15/05, Tom Hoefakker [EMAIL PROTECTED] wrote:
Perhaps while we're dealing with piped log process/pipe management
perhaps we can take care of this one at the same
Full Article:
http://service.spiegel.de/cache/international/0,1518,344374,00.html
13 matches
Mail list logo
