On Fri, Apr 16, 2004 at 11:53:28AM -0600, Michael Loftis wrote: > Not system wide, re-read my message. I'm using that. That only works for > PAM apps. init isn't a PAM app. somewhere between the kernel firing init > and initscripts getting run something is screwing up that limit. And there > has beena change between 'woody' and 'sarge' since sarge isn't screwed up > like this.
My apologies. Try putting ulimit in /etc/init.d/rc maybe? Brian > --On Friday, April 16, 2004 11:19 +0100 Brian Brazil > <[EMAIL PROTECTED]> wrote: > > >On Thu, Apr 15, 2004 at 02:10:37PM -0600, Michael Loftis wrote: > >>For whatever reason debian stable somewhere somehow defaults to a > >>RLIMIT_NPROC (max user processes) of 256. This is fine for a desktop > >>but absurd for a server. I have yet to find a good way to fix this, > >>but I still don't see what is changing it. It should be something like > >>7000 on the machines I'm trying to fix it on, so something inside of > >>debian is changing it. My unstable boxes do not show this behaviour > >>(they come up with unlimited, which is fine for my servers except my > >>shell server). > >> > >>I can't find where the heck this is getting set, nor even where to > >>change it. Something is setting it different from the kernel default > >>of max_threads / 2 (see kernel/fork.c) but i'll be deviled if i can > >>find what. I can and do use pam_limits.so/limits.conf for logins, but > >>for daemon startup I need to fix this and know it's not ending up at > >>256. > >> > >>any help/ideas? > > > >/etc/pam.d pam_ulimit.so > >/etc/security/limits.conf > > > >Brian > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
