Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Tue, 9 Oct 2012 02:58:02 +0000 (UTC)
From: "Alex Huang (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <1961057271.12495.1349751482637.JavaMail.jiratomcat@arcas>
In-Reply-To: <1269010712.12467.1349750642682.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-295) Add instructions to modify
 limits.conf in installation directions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Huang updated CLOUDSTACK-295:
----------------------------------

    Fix Version/s:     (was: 4.0.0)
                   4.1.0
    
> Add instructions to modify limits.conf in installation directions
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-295
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-295
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Doc
>    Affects Versions: pre-4.0.0
>            Reporter: David Nalley
>            Priority: Blocker
>             Fix For: 4.1.0
>
>
> Changing config files was deemed too unsavory to be done in a automated manner so that was removed from the spec file. 
> Thus we need to add a section to installation documents that discusses modifying /etc/security/limits.conf
> Here is what was in the spec file, this should only be for the management server. 
> # set max file descriptors for cloud user to 4096 sed -i /"cloud hard nofile"/d
> /etc/security/limits.conf sed -i /"cloud soft nofile"/d /etc/security/limits.conf
> echo "cloud hard nofile 4096" >> /etc/security/limits.conf echo "cloud soft
> nofile 4096" >> /etc/security/limits.conf rm -
> rf %{_localstatedir}/cache/%{name}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira