*               -       memlock         0

On Tue, Nov 30, 2010 at 4:40 AM, Nate McCall <n...@riptano.com> wrote:
> What does the current line(s) in limits.conf look like?
>
> On Mon, Nov 29, 2010 at 2:01 AM,  <jasonmp...@gmail.com> wrote:
>> I checked and /etc/security/limits.conf on redhat supports zero (0) to
>> mean unlimited.  Here is the sample from the man page.  Notice the
>> soft core entry.
>>
>> EXAMPLES
>>       These are some example lines which might be specified in
>>       /etc/security/limits.conf.
>>
>>       *               soft    core            0
>>       *               hard    rss             10000
>>       @student        hard    nproc           20
>>       @faculty        soft    nproc           20
>>       @faculty        hard    nproc           50
>>       ftp             hard    nproc           0
>>       @student        -       maxlogins       4
>>
>>
>>
>> On Mon, Nov 29, 2010 at 6:51 AM, Jason Pell <jasonmp...@gmail.com> wrote:
>>> Ok that's a good point i will check - I am not sure.
>>>
>>> Sent from my iPhone
>>> On Nov 29, 2010, at 5:53, Tyler Hobbs <ty...@riptano.com> wrote:
>>>
>>> I'm not familiar with ulimit on RedHat systems, but are you sure you
>>> have ulimit set correctly? Did you set it to '0' or 'unlimited'?  I ask
>>> because on a Debian system, I get this:
>>>
>>> tho...@~ $ ulimit -l
>>> unlimited
>>>
>>> Where you said that you got back '0'.
>>>
>>> - Tyler
>>>
>>> On Sun, Nov 28, 2010 at 1:15 AM, Jason Pell <ja...@pellcorp.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I have selinux disabled via /etc/sysconfig/selinux already.  But I did
>>>> as you suggested anyway, even restarted the whole machine again too
>>>> and still no difference.  Do you know if there is a way to discover
>>>> exactly what this error means?
>>>>
>>>> THanks
>>>> Jason
>>>>
>>>> On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <n...@riptano.com> wrote:
>>>> > This might be an issue with selinux. You can try this quickly to
>>>> > temporarily disable selinux enforcement:
>>>> > /usr/sbin/setenforce 0  (as root)
>>>> >
>>>> > and then start cassandra as your user.
>>>> >
>>>> > On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <jasonmp...@gmail.com>
>>>> > wrote:
>>>> >> I restarted the box :-) so it's well and truly set
>>>> >>
>>>> >> Sent from my iPhone
>>>> >> On Nov 26, 2010, at 17:57, Brandon Williams <dri...@gmail.com> wrote:
>>>> >>
>>>> >> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com>
>>>> >> wrote:
>>>> >>>
>>>> >>> Hi,
>>>> >>>
>>>> >>> I have set the memlock limit to unlimited in /etc/security/limits.conf
>>>> >>>
>>>> >>> [devel...@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
>>>> >>> 0
>>>> >>>
>>>> >>> Running as a non root user gets me a Unknown mlockall error 1
>>>> >>
>>>> >> Have you tried logging out and back in after changing limits.conf?
>>>> >> -Brandon
>>>> >
>>>
>>>
>>
>

Reply via email to