-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 12 November 2002 04:30, Roy Souther wrote: > Try using /etc/security/limits.conf to restrict the amout of RAM, CPU > usage they can have. > Make sure they can not install binarys into places like /usr/bin or > /usr/local make them run their binaries for $HOME/bin and set up disk > quotas so they don't use to much space.
this is exactly what i thought when reading the parent. only a couple things to add: stop using ext2 on a server with that much disk that may be brought to its knees because of development happening on it. use a journaled filesystem like ext3 (which you can upgrade ext2 from w/out reformatting) and your fschecks will take up a lot less of your time ;-) as for large files, as long as you are using a 2.4 kernel you will big file support, allowing files up to 16terabytes even on 32 bit platforms. more info can be had at: http://www.suse.de/~aj/linux_lfs.html take care and best of luck w/your crashy server. of course, you could always just take to whipping the developers whenever the system goes down. i understand developers respond well to frequent and savage beatings. ;-) - -- Aaron J. Seigo GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 "Everything should be made as simple as possible, but not simpler" - Albert Einstein -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90ZLq1rcusafx20MRAmbeAJ94BCny6Xsn6wIWFDZoClnwjEfgdgCeKnMT Mi9crB4ssq2uCaYzltHksFs= =hMJD -----END PGP SIGNATURE-----
