Brian Pane wrote:
>
> Greg Ames wrote:
> >ooops, I see what you mean about an fd per module per child. That bites big
> >time. I'm very surprised to see them.
> >
> >httpd 97082 nobody txt VREG 13,131072 114273 684290
> >/usr/local/apache2_0_28/modules/mod_include.so
> >httpd 97082 nobody txt VREG 13,131072 97082 684314
> >/usr/local/apache2_0_28/modules/mod_autoindex.so
> >httpd 97082 nobody txt VREG 13,131072 52172 684328
> >/usr/local/apache2_0_28/modules/mod_dir.so
> >httpd 97082 nobody txt VREG 13,131072 49046 684316
> >/usr/local/apache2_0_28/modules/mod_asis.so
> >
>
> That looks normal to me. Those mmap'ed libraries aren't associated
> with file descriptors (per the "txt" instead of an fd number in the
> 4th column), so they don't count against the process's fd limit.
whew! I'm glad to hear it. Brian B said he installed a new rsync yesterday, so
that could be the culprit. I think we're hitting a system-wide limit rather
than a per process limit. The log messages look like:
> file: table is full
> file: table is full
> file: table is full
> file: table is full
> Jan 29 01:16:15 daedalus last message repeated 60 times
plus there's a number of rsync seg faults.
Does anyone know if there's a way to up the system limit for fd's on FreeBSD
without recompiling the kernel?
Greg
