Request 285 was acted upon.
This is a comment. It is not sent to the Requestor(s).
_________________________________________________________________________
URL: https://rt.openpkg.org/id/285
Ticket: [OpenPKG #285]
Subject: postfix/ulimit vs. fsl/file channel
Requestors: [EMAIL PROTECTED]
Queue: openpkg
Owner: Nobody
Status: new
Transaction: Comments added by thl
Time: Mon Oct 27 13:14:46 2003
_________________________________________________________________________
> [thl - Mon Oct 27 10:59:02 2003]:
>
> [...] Cleanup daemon enforces message
> size limits by using system call ulimit(2) with value taken from
> message_size_limit in main.cf. [...]
>
The problem and the solution - better called a workaround - is similar to the incident
discussed in http://archives.neohapsis.com/archives/postfix/2002-10/0288.html
where Nick Simicich reports "[...] I showed that this limit was being set
by postfix, as a side effect of the default setting of mailbox_size_limit. It is easy
for people to bypass, of course, by setting the parameter to zero [...]"
It is clear that under the circumstances described herein no code that is executed
after a hard limit was set will ever be able to write a file larger than the limit.
Even if the code would know about ulimit(2) it cannot revert the limit unless it runs
as root. This affects all code that tries to write to a file and fsl is only one
victim. The situation is a dead end for the current fsl-1.x implementation and is not
likely to change soon.
For OpenPKG this means we need to try to tweak the affected postfix package to
overcome this limitation.
--
Thomas Lotterer
OpenPKG Developer
[EMAIL PROTECTED]
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
