At 16:13 30-09-97 -0700, Brian Behlendorf wrote:
>nph- scripts without end (i.e. all those "server-push" scripts,
>multipart/x-mixed-replace, etc) will seriously not end; a connection close
>by the client won't be noticed, and the nph program will spin indefinitely.
> They don't burn much CPU or memory; they just sit there, bound to a child,
>and when a graceful restart is attempted in order to rotate logs, the child
>doesn't time out and stays in "G" mode, which also means it never lets go
>of its file descriptor to the logs. This is the current code base, and
>it's a recent (last couple of weeks) problem, but I haven't narrowed it
>further. It'd be wise to test it with 1.2.4 and 1.3 as of right before the
>nph- changes.
I've seen this happen in 1.2.4 for sure...
Elizabeth Mattijsen
xxLINK Internet Services
|