On Fri, May 09, 2014 at 12:06:15AM +0000, Mitch Patenaude wrote: > I figured out part of this: limits.conf is read by pam_limits.so, so > until you log in, it isn't effective. I don't have an elegant solution, > but my hackish solution so far is just to put a "ulimit -n 65536" into > the init script. Does anybody have a better (more elegant) solution? You can either do that or, maybe, use "su" or "runuser" to cause PAM to be called. -- rgds Stephen _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: Processes launched from rc*.d and ulimit -n
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: Processes launched from rc*.d and ulimit -n
- From: Stephen Harris <lists@xxxxxxxxxx>
- Date: Thu, 8 May 2014 20:10:07 -0400
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <7880CCDD484B07498DB786C5CAFAFD646EC7F8C5@EXCH05-SC.corp.shutterfly.com>
- User-agent: Mutt/1.4.2.2i
- References:
- Processes launched from rc*.d and ulimit -n
- From: Mitch Patenaude
- Re: Processes launched from rc*.d and ulimit -n
- From: Mitch Patenaude
- Processes launched from rc*.d and ulimit -n
- Prev by Date: Re: plug in phones, speaker does not mute.
- Next by Date: CentOS-announce Digest, Vol 111, Issue 5
- Previous by thread: Re: Processes launched from rc*.d and ulimit -n
- Next by thread: Re: Processes launched from rc*.d and ulimit -n
- Index(es):
 |