On 12/25/06, David Faure <email address hidden> wrote:
> Surely all the tools can't be changed to ignore SIGXFSZ, the right fix
> is in the vfat code of the linux kernel, isn't it?
As a matter of fact my memories were about linux 2.4, I had the
problem with netatalk.
In my understanding, after a quick look at linux 2.6 source code, it's
by default for all file systems write, cf. mm/filemap.c.
On the other hand SIGXFSZ is sent when files ulimit is reached so
maybe tools should
deal with it.
On 12/25/06, David Faure <email address hidden> wrote:
> Surely all the tools can't be changed to ignore SIGXFSZ, the right fix
> is in the vfat code of the linux kernel, isn't it?
As a matter of fact my memories were about linux 2.4, I had the
problem with netatalk.
In my understanding, after a quick look at linux 2.6 source code, it's
by default for all file systems write, cf. mm/filemap.c.
On the other hand SIGXFSZ is sent when files ulimit is reached so
maybe tools should
deal with it.