On 27/12/2010 14:12, Torbjorn Granlund wrote: > Peter Korsgaard <jac...@sunsite.dk> writes: > >>>>>> "Joern" == Joern Rennecke <amyl...@spamcop.net> writes: > > Hi, > >>> Sorry, I will. Was away for the holidays. > > Joern> I wonder: what is the maximum CPU time a healthy configure would > take? > > Less than this. It seems like my workaround to not end up in that situation > didn't work - Will fix. > > I use "ulimit -t SOMELIMIT" for my automated builds. The timeouts are > generous, but when a timeout is hit, I get an automated message. (Using > generous timeouts without raising an error is bad, you end up using too > much resources for each automated build, and might ever notice the > problem.)
At http://gcc.gnu.org/wiki/CompileFarm, in the "Usage" section, it advises: > Use the command ulimit to reduce the risk of a DOS attack by your > script/program. Example: ulimit -S -t 3600 -v 2000000 -u 1200 Maybe we should put that in the global /etc/profile so that people who want to do something unusual have to override their ulimits manually, rather than hope everyone will remember to ulimit their scripts? cheers, DaveK _______________________________________________ Gcc-cfarm-users mailing list Gcc-cfarm-users@gna.org https://mail.gna.org/listinfo/gcc-cfarm-users
