The overall desired effect is to limit a user's use of certain resources -- CPU, memory, disk, etc. It's not easy to "jail" a user in this manner. Meaning, we can't say that, if there are 10 users logged on, give these users about 10% of CPU resources. A user can easily bring down the system by doing something CPU intensive -- e.g. using OO.org to edit a complex document or visiting a Flash-heavy site. cant we use limits.conf to restict users "access" to the server's resources? |
-- Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
