We had a problem with this at one point. I believe the culprit was pam. When you log into the box via ssh it calls pam to authenticate. This switches your user in the process, reducing your ulimit back to 1024. By the time you've gotten a shell your ulimit max is once again 1024. We found the settings did work if you did one of: A) Logged in directly from the console, B) did a su - username as root, C) started the command in an init script with su - username -c <startup command> I don't remember how we got it to work from a ssh session though. We may have given up and just done our start / stops with init scripts. Russell On 6/16/06, Yard, John <jyard@xxxxxxxxxxxx> wrote:
Did not work, JYard -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of joe@xxxxxxxxxxxxxxxxx Sent: Friday, June 16, 2006 1:57 PM To: redhat-list@xxxxxxxxxx Subject: AW: ulimit change still does not persist across system boot Take a loot at "/etc/security/limits.conf" ... Set there something like: USERNAME - nofile 8192 ...this should work cu, Joe PS: the file-mode shall be 644... cross-check that also ;-) -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
