Red Hat Bugzilla – Bug 495035
/etc/profile overrides limits.conf core dump size setting
Last modified: 2009-06-18 08:42:46 EDT
/etc/profile, provided by this setup package imposes ulimits on all shells that use this file. This is incorrect. Policy is dicated,currently, by /etc/security/limits.conf or /etc/security.limits.d, certainly not a bash script.
Please remove the ulimit here.
Settings in limits.conf affect newly spawned shells
Settings in limit.conf for core files have no affect on newly spawned shells
Other people have this problem as well:
(older, but still relevant)
Thanks for suggestion, it is necessary to keep core dumps disabled by default (consider production machines). Additionally - it's not only /etc/profile, but /etc/csh.cshrc as well (setting coredumpsize limit to 0). You could easily override those settings by customized script in /etc/profile.d/ anyway... (as was recommended in one of the discussion threads you provided)
I agree that the current situation should be improved somehow. Nowadays pam (where is default /etc/security/limits.conf) is installed almost everywhere, so in the case of the uncomented default setting core 0 in limits.conf, it should be safe to remove that from setup profile/csh.cshrc scripts. Adding pam maintainer to cc...
If I am right (I just tested it on rawhide) the kernel default for the core soft limit already is 0. So it should be safe to drop the setting from the profile/csh.cshrc scripts.
Thanks Tomas, I tried that on rawhide machine as well, it's really set to 0 there. But on F10 machine it's nonzero, so those ulimit / limit commands should be kept there. Will remove this stuff from Rawhide setup and close that bugzilla RAWHIDE or NEXT_RELEASE, as I guess it's not good idea to change that in F-10.
Closing RAWHIDE, already built there as setup-2.8.3-1.fc12 . I do not plan to update F-10/F-11 setup, unless the kernel default for core soft limits will be changed to 0 there.
*** Bug 506675 has been marked as a duplicate of this bug. ***