(In reply to Jim Jagielski from comment #20)
> But it is NOT silently. It is logged at APLOG_ERR to allow the admin to know
> that it happened and to decide if it is, or is NOT, a problem.
So truncation does not have to happen, and most of the time even fail.
Exposing upper resources is most of the time EVIL...
This commit is at best a workaround, and in my opinion a big and dangerous regression.
(In reply to Jim Jagielski from comment #20)
> But it is NOT silently. It is logged at APLOG_ERR to allow the admin to know
> that it happened and to decide if it is, or is NOT, a problem.
So truncation does not have to happen, and most of the time even fail.
Exposing upper resources is most of the time EVIL...
This commit is at best a workaround, and in my opinion a big and dangerous regression.