Re: More FD's in 2.0.33

Dancer (dancer@brisnet.org.au)
Wed, 25 Mar 1998 16:04:18 +1000


It'd be very nice to make the FD limits into 'standard' configuration
options. IMO.

D

Jon Lewis wrote:
>
> On Tue, 24 Mar 1998, Shane Anderson wrote:
>
> > I'm looking for the *RIGHT* way to get more open files in 2.0.33.
> > I've downloaded Michael O'Reilly's patch, but it had problems with
> > portmapper (on RedHat 5.0 w/ all the latest updates) crapping
> > out--apparently due to bad file descriptors, which I think was due to
> > the dynamic allocation done in this patch. So, since then I've tried
> > to just change the #define's that I believe matter, namely:
>
> You need some variation of the kmalloc patch, otherwise you risk
> overflowing space in the kernel, and then bad things happen. Someone had
> mentioned that even with the limit raised to 3000, the default should
> still be set to 256, and that programs should use setrlimit to raise the
> limit when necessary. That may fix your problem.
>
> ------------------------------------------------------------------
> Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
> Network Administrator | be proof-read for $199/message.
> Florida Digital Turnpike |
> ______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key____
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu

-- 
Did you read the documentation AND the FAQ?
If not, I'll probably still answer your question, but my patience will
be limited, and you take the risk of sarcasm and ridicule.

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu