Re: cp/mv/dd to handle SIGXFSZ?

[Philip Rowlands]

On Mon, 9 Apr 2007, Micah Cowan wrote:

> Users report having this problem when they copy to (e.g.) vfat 
> systems, but not ext3, so it seems to be FS-related. Even if it did 
> turn out to be usage limit, I would think the problem would be the 
> same: it's much more useful (IMO) to issue a diagnostic and attempt to 
> proceed, than to coredump. :p

I understand the problem, but I'm challenging the assumption that the 
Linux kernel is doing the right thing. If there's no RLIMIT_FSIZE 
restriction, why should the process be sent a SIGXFSZ? (I'm neither a 
kernel programmer or standards guru - I'd just like to see where this is 
documented.)

Perhaps most POSIX systems behave this way... I'm afraid I don't have 
any others handy to check.


Cheers,
Phil