Theo de Raadt wrote [2012-03-28 22:44+0200]: > If software cannot cope intelligently with soft resource limits, > then such software is probably broken. > > Otherwise, let's just remove the entire resource limit subsystem, ok?
I found out that i miss some kind of "physical" keyword. The impossibility to compile insn-attrtab in my VM was caused by insufficient memory, and gcc(1) being unable to detect that it effectively entered an endless loop. Once i've lowered the softlimit i got a clear 'virtual memory exhausted' message. So some kind of automatic adjustment of the limits to physically present mem (+swap) would have helped a bad admin here. Maybe i find time next week to write a small MAX_RETRY patch for gcc. --steffen Forza Figa!
