I just would like to say, that this is an extremely ill-thought out change. It's a change to basic behavior thats been in place for years and years, and makes core files even MORE problematic for disk space as they don't overwrite each other. Is this a ReddHat change, or a linux kernel change? If RedHat came up with this, I think they are being extremely foolish. ----- Original Message ----- From: "Jag" <agrajag@dragaera.net> To: <redhat-devel-list@redhat.com> Sent: Thursday, December 12, 2002 7:29 PM Subject: Re: How to get RedHat 8.0 to allow core dump files > On Thu, 2002-12-12 at 18:54, Dan Winslow wrote: > > Platform is a fresh install of RedHat 8.0. I have > > ulimit -c unlimited > > in /etc/profile. I have write perms to the current dir. A test program > > compiled with gcc that does a 'strcpy(0,0)' seg faults but does not > > core > > dump. I have searched all day on the web, finding nothing but ulimit > > settings. Any advice would be highly appreciated. > > > > Did you make sure to get rid of the ulimit line that was already in > /etc/profile? Also, once you have the shell started, run 'ulimit -c' > to see what it says. When I do 'ulimit -c unlimited' in the shell, I > can dump core on 8.0 without problems. > > > Jag > > > > _______________________________________________ > Redhat-devel-list mailing list > Redhat-devel-list@redhat.com > https://listman.redhat.com/mailman/listinfo/redhat-devel-list > _______________________________________________ Redhat-devel-list mailing list Redhat-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-devel-list
