Bernd Jendrissek <bernd.jendrissek@???> wrote: > Phil Pennock wrote:
>> This is the entire problem -- the transport runs as non-root, so can
>> only raise the core size current ulimit to the configured maximum. Only
>> root can raise maximum values. This is kernel-enforced.
>>
>> But Exim sets both the current *and* the maximum values to 0.
>>
>> If Exim set only the current value, leaving the maximum as
>> RLIM_INFINITY, then Jorg could indeed do exactly as you say. It's
>> because Exim is taking an action which only root can reverse that
>> there's an issue.
>>
> Since it's an external program that's crashing, why not write a
> setuid-root wrapper that raises RLIMIT_CORE, goes back to an
> unprivileged user, and exec's the "real" program?
When I start coding, I would write a wrapper library that silently dropps
the setrlimit() call and run exim with this library, because one gives me
a guarantee that the exim code after the setrlimit() is fine and will
never crash exim. Then I would be able to catch this bug, if it isn't
reproducable.
Bye, Jörg.
--
Der Mensch hat die Atombombe erfunden.
Keine Maus der Welt käme auf die Idee, eine Mausefalle zu konstruieren.
