<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unable to set ulimit for a user in Red Hat ES 5. in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/unable-to-set-ulimit-for-a-user-in-red-hat-es-5/m-p/4675206#M41872</link>
    <description>Thanks so much, Matti! That worked :-).</description>
    <pubDate>Mon, 16 Aug 2010 12:00:37 GMT</pubDate>
    <dc:creator>mpua</dc:creator>
    <dc:date>2010-08-16T12:00:37Z</dc:date>
    <item>
      <title>Unable to set ulimit for a user in Red Hat ES 5.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unable-to-set-ulimit-for-a-user-in-red-hat-es-5/m-p/4675204#M41870</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I've set a nofiles hard limit in /etc/security/limits.conf this way:&lt;BR /&gt;&lt;BR /&gt;*               hard     nofiles         8192&lt;BR /&gt;&lt;BR /&gt;Then, I put the following setence in .bash_profile of user "carlos":&lt;BR /&gt;&lt;BR /&gt;# .bash_profile&lt;BR /&gt;&lt;BR /&gt;# Get the aliases and functions&lt;BR /&gt;if [ -f ~/.bashrc ]; then&lt;BR /&gt;        . ~/.bashrc&lt;BR /&gt;fi&lt;BR /&gt;&lt;BR /&gt;# User specific environment and startup programs&lt;BR /&gt;&lt;BR /&gt;PATH=$PATH:$HOME/bin&lt;BR /&gt;&lt;BR /&gt;export PATH&lt;BR /&gt;&lt;BR /&gt;ulimit -n 8192&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;When I log as carlos from root (su - carlos) my user carlos sets the ulimit correctly as 8192 but when I log straight as carlos through SSH my user ends with nofiles ulimit as 1024, giving me the following error trying to execute the "ulimit -n 8192" line:&lt;BR /&gt;&lt;BR /&gt;bash: ulimit: open files: cannot modify limit: Operation not permitted&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Whats the point with this??? Im turning crazy.</description>
      <pubDate>Mon, 16 Aug 2010 11:16:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unable-to-set-ulimit-for-a-user-in-red-hat-es-5/m-p/4675204#M41870</guid>
      <dc:creator>mpua</dc:creator>
      <dc:date>2010-08-16T11:16:14Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to set ulimit for a user in Red Hat ES 5.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unable-to-set-ulimit-for-a-user-in-red-hat-es-5/m-p/4675205#M41871</link>
      <description>Your SSH daemon has been started using the old ulimit values, so all child processes of sshd will inherit the old values. &lt;BR /&gt;&lt;BR /&gt;Only root has the special privilege to increase a hard ulimit... and apparently the main sshd process gives up this privilege for security, so the old ulimit can be increased only if the new SSH session logs in as root.&lt;BR /&gt;&lt;BR /&gt;After increasing the hard ulimit, restart the sshd daemon using a session that already has the new hard limit. (Rebooting the system would work too, but it's overkill...)&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Mon, 16 Aug 2010 11:43:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unable-to-set-ulimit-for-a-user-in-red-hat-es-5/m-p/4675205#M41871</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2010-08-16T11:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to set ulimit for a user in Red Hat ES 5.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unable-to-set-ulimit-for-a-user-in-red-hat-es-5/m-p/4675206#M41872</link>
      <description>Thanks so much, Matti! That worked :-).</description>
      <pubDate>Mon, 16 Aug 2010 12:00:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unable-to-set-ulimit-for-a-user-in-red-hat-es-5/m-p/4675206#M41872</guid>
      <dc:creator>mpua</dc:creator>
      <dc:date>2010-08-16T12:00:37Z</dc:date>
    </item>
  </channel>
</rss>

