Re: Preventing a single student programmer from choking the whole server.

2017-05-04 Thread Josh Roden
Hi Yedidyah Loved the SIGSTOP/SIGKILL approach - simple but awsome. I seems to be working. Thanks for everyone's input. Josh On Sun, Apr 23, 2017 at 9:18 AM, Yedidyah Bar David wrote: > On Sat, Apr 22, 2017 at 12:51 PM, Josh Roden wrote: > > Hi > > I see

Re: Preventing a single student programmer from choking the whole server.

2017-04-22 Thread Josh Roden
Hi I see some explanation about cgroups on Centos 6 here: https://www.digitalocean.com/community/tutorials/how-to-limit-resources-using-cgroups-on-centos-6 I will check about its implementation for Centos 6 and update my post. Thanks for giving a direction. Josh On Fri, Apr 21, 2017 at 4:27 PM,

Re: Preventing a single student programmer from choking the whole server.

2017-04-21 Thread guy keren
how about using cgroups, putting each user's login shell in a cgroup that cannot use more then X% of the whole CPUs. this will affect all processes spawned under the user's shell. --guy On 04/21/2017 03:07 PM, Josh Roden wrote: Hi server setup: -- Centos 6 32GB RAM 16

Preventing a single student programmer from choking the whole server.

2017-04-21 Thread Josh Roden
Hi server setup: -- Centos 6 32GB RAM 16 Cpu's 70 students max I am using /etc/security/limits.conf to prevent the students from choking the whole server but sometimes one student will write a very bad program that somehow runs itself again and again - so fast that "killall" and