| 1 |
On 2/27/07, Boyd Stephen Smith Jr. <bss03@××××××××××.net> wrote: |
| 2 |
> On Monday 26 February 2007, Dan Farrell <dan@×××××××××.cx> wrote about 'Re: |
| 3 |
> [gentoo-user] Avoiding core dumps': |
| 4 |
> > On Sun, 25 Feb 2007 18:39:27 -0500 |
| 5 |
> > David Relson <relson@×××××××××××××.com> wrote: |
| 6 |
> > > On Sun, 25 Feb 2007 22:12:49 +0100 |
| 7 |
> > > Christoph Nodes wrote: |
| 8 |
> > > > I am using sys-libs/pam-0.78-r5. |
| 9 |
> > > |
| 10 |
> > > As best I know, it's the ulimit setting that's relevant and pam is not |
| 11 |
> > > involved. |
| 12 |
> > |
| 13 |
> > AFAIK, pam is only for Authentication. |
| 14 |
> |
| 15 |
> There are a lot of tangential issues (like limits) that were traditionally |
| 16 |
> controlled by the authentication "stack" on unix. PAM allows you to |
| 17 |
> replace all of this, so there are indeed PAM modules that control limits. |
| 18 |
|
| 19 |
Thank you all for your answers. |
| 20 |
|
| 21 |
I added 'ulimit -c 0' to /etc/profile but I am not completely happy |
| 22 |
with this. Why do I have to change anything? I always thought not |
| 23 |
alowing core dumps would be the default behaviour. |
| 24 |
|
| 25 |
I guess KDE's crash handler could also responsible for changing the |
| 26 |
core dump limit. I'll have a look. |
| 27 |
-- |
| 28 |
gentoo-user@g.o mailing list |
Archives