Micah Cowan wrote:
> Alan Cox wrote:
>>> [XSI] [Option Start] If the request would cause the file size to
>>> exceed the soft file size limit for the process and there is no room
>>> for any bytes to be written, the request shall fail and the
>>> implement
s it for when a written file exceeds the process's
resource limits. I'd like to limit SIGXFSZs to the bare minimum required
by SUS.
Patch sent per http://lkml.org/lkml/2007/4/10/302
Signed-off-by: Micah Cowan <[EMAIL PROTECTED]>
---
fs/ncpfs/file.c|2 --
fs/reiserfs/file.
Hello,
I would like to object to a non-standard and, IMHO, ill-advised
application of SIGXFSZ to non-rlimit-related filesize limits, and
request that its use be minimized as much as possible. SUSv3 does not
sanction its use in any situation other than that of exceeding the "soft
file size lim
Alan Cox wrote:
[XSI] [Option Start] If the request would cause the file size to exceed
the soft file size limit for the process and there is no room for any
bytes to be written, the request shall fail and the implementation shall
generate the SIGXFSZ signal for the thread. [Option End]
>>>
4 matches
Mail list logo