[ale] user limits

[Tim Meanor]

I believe that when a user hits a soft limit, the same thing happens
as when they hit a hard limit - in the case of a memory soft limit, a
segfault.  The difference is that a soft limit can be changed by a
non-root user on-the-fly, up to the hard limit.

-Tim

On Tue, Oct 7, 2008 at 2:04 PM, Jim Kinney <jim.kinney at gmail.com> wrote:
> xmessage is the way to do it. Now to find a daemon that can do the deed
> and deliver an intelligent message....
>
> or write one which is looking like the real solution. Need to find
> _where_ the soft limit signal is written (/var/log/message? STDOUT?)
>
> On Tue, 2008-10-07 at 13:55 -0400, James Sumners wrote:
>> Launch everything via a script that checks the limit and then issues
>> an xmessage[1]?
>>
>> [1] -- http://www.manpagez.com/man/1/xmessage/
>>
>> On Tue, Oct 7, 2008 at 1:45 PM, Jim Kinney <jim.kinney at gmail.com> wrote:
>> > When a system uses pam, the file (typically) /etc/security/limits.conf
>> > can control limits for things like resident set size, stack size, number
>> > processes, login count, etc.
>> >
>> > What happens when a user hits a soft limit? A hard limit means the
>> > operation is not completed and/or fails.
>> >
>> > I'm looking for a way to notify users that they are pushing their luck
>> > opening another (eg - firefox) application as they are running out of
>> > ram.
>> >
>> > Jim Kinney
>> >
>> > _______________________________________________
>> > Ale mailing list
>> > Ale at ale.org
>> > http://mail.ale.org/mailman/listinfo/ale
>> >
>>
>>
>>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>