On Wed, Jul 24, 2013 at 03:04:28PM +0200, Landry Breuil wrote: > That point has been a long-standing discussion among developers, and > a consensus hasn't been reached yet. Note that iirc, chromium wrapper > automatically bumps ulimit -d at startup to workaround such issues..
Actually the main current issue is that 'one size does NOT fit all'. you don't want the same data size on an amd64 with 6G of physical memory and a lowly sparc with 32M... That's the main issue with login.conf, and this will probably require a bit of code to get properly fixed eventually.
