[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Setting memory limits in lts.conf



oops

I have been editing lts.conf a lot the last few days - got it on the
brain :-/

but limits.conf looks like something that could be of real use in this
environment. I've wondered before if someone wanted to, could they
purposely use up all the RAM.

BTW - I'm using the Term 150 that you sell on your site here at home.
Even hanging off a very modest "server" it is very quick. Very nice
device.

John


On Sat, 2005-07-23 at 12:50 -0400, Jim McQuillan wrote:
> John,
> 
> It's interesting, but i'm wondering why your subject line suggests
> setting it in lts.conf.  That wouldnt' be the correct place, as the
> purpose of the lts.conf file is to configure various attributes of the
> thin client.  The client doesn't know anything about the user or
> applications, so it wouldn't have any ability to enforce such limits.
> 
> Jim McQuillan
> jam Ltsp org
> 
> 
>  On Sat, 23 Jul 2005, John Baillie wrote:
> 
> > Has anyone heard of, or tried the following?
> >
> >
> > " I strongly suggest you set suitable memory limits
> > in /etc/security/limits.conf. I use:
> >
> > @users soft rss 512000
> > @users soft memlock 256000
> > @users soft as 768000
> > # Set to 7168 by RH defaults
> > # users soft nproc 5000
> >
> > Just to stop users from forkbombing the system accidentally, or a
> > runaway process from eating all the physical RAM and forcing the system
> > into heavy swapping. It works extremely well. Adapt the above, of
> > course, to your memory allocations etc. "
> >
> >
> >
> > _______________________________________________
> > K12OSN mailing list
> > K12OSN redhat com
> > https://www.redhat.com/mailman/listinfo/k12osn
> > For more info see <http://www.k12os.org>
> >
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
> 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]