Error: Cannot update core dump limit

Arran Cudbard-Bell a.cudbardb at freeradius.org
Wed Jul 13 15:13:12 CEST 2016


> On 13 Jul 2016, at 08:58, Alan DeKok <aland at deployingradius.com> wrote:
> 
> On Jul 13, 2016, at 8:06 AM, Jakob Hirsch <jh at plonk.de> wrote: dumps.
>> 
>> 
>> And how would you suggest I should do that? freeradius is started as
>> root, so the capability is there at start time.
> 
>  If you set "allow_core_dumps = yes" it should work.
> 
>> As I wrote, the code explicitely sets the hard limit for the core size
>> to zero, so there is no chance for the unprivileged freeradius user to
>> raise them again. Why is the server doing that??
> 
>  Honestly... no idea.
> 
>  All of that debugger / core dump code was re-written by Arran.   It *should* work, but I've had all kinds of problems with it.

Even split between code issues, PEBCAK, poor communication.

-Arran

Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS Development Team

FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 872 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freeradius.org/pipermail/freeradius-devel/attachments/20160713/d2c2ad6b/attachment.sig>


More information about the Freeradius-Devel mailing list