Re: Xinetd and file descriptor limits?
"John Minnihan" <[email protected]> Tue, 6 Jan 2004 15:26:18 -0700 (MST)
| Newsgroups | gmane.network.xinetd |
|---|---|
| Message-ID | <[email protected]> |
Thanks for the detailed reply. See inline comments/questions below. Steve G said: > I also think there is another limit settable by sysctl. If you > get past this, I think xinetd only requests 1024 descriptors. You > would need to tweek it to set the rlimit higher for the per > process limit. Can you provide any guidance on tweaking the rlimit? I can grok new things pretty well, but a starting point is always handy. >>How is the output of '-d' captured for review? > > I startup x and look at it though a terminal window after setting > the number of lines for it to buffer. Ah, ok. > >>I suspect I am hitting the system or user default of 1024 file >>descriptors, but I am curious why that number (1024) doesn't >>quite match the number of services successfully started, 1016. > > xinetd uses a couple for internal messaging, stdin,stdout,stderr > are all set to /dev/null and then glibc also leaks descriptors in > pmap_set, and then error logging. So that's a reasonable number. Good. > > Take a look in init.c. Look for setfd_limit(). You may want to > tweek that function to request more descriptors. I took a look at init.c and saw the function, but must admit I haven't any idea how to tweak it. I don't see where it gets it value(s) - from one of the includes? -- John Minnihan Founder & Chief Architect https://www.freepository.com Free software development tools since 1999