2012/5/5 Steven Chamberlain <ste...@pyro.eu.org>: > Upstream does it that way, but I'm not sure if GNU/kFreeBSD does (I see > no mention of ulimit in /etc?). But if so, it would explain why this > was reproducible on buildd's and not on the asdfasdf porter box.
ulimit is just the user interface. This is set by PAM, see pam_limits(8) and setrlimit(2). > Raising DFLSIZ seems like the best way to me, as the buildd's will need > it, and some daemons like mysql or postgres seem to want a larger data > size anyway. I'm on your side. I had this discussion with upstream already :-) > Even with 'ulimit -d unlimited', kfreebsd-i386 is bounded by MAXDSIZ = > 512 MiB whereas cmor would need ~700ish. I suppose that and DFLDSIZ > could be raised to 1 GiB on kfreebsd-i386 to try to fix this, but no > higher as explained in: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598745#20 If it can be set to 1 GiB, why hasn't upstream done this? I think it wouldn't be a good idea to increase this limit in Debian unless upstream does. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caofdtxovm8y+wumecvvybf5sjgcq8nrwya9jp8bp1envq...@mail.gmail.com
