Re: [boost] [filesystem] truncate() function?

Subject: Re: [boost] [filesystem] truncate() function?
From: dherring_at_[hidden]
Date: 2009-10-14 12:18:28

On Wed, 14 Oct 2009, Beman Dawes wrote:

> Does the POSIX implementation need to do anything to cope with the
> possibility of a SIGXFSZ signal? If so what?

Don't do anything.  Signal handlers are global; so it is generally poor 
form for a library to install one unless explicitely requested.

FYI, the linux manpages say
http://www.kernel.org/doc/man-pages/online/pages/man7/signal.7.html
""
        Next the signals not in the POSIX.1-1990 standard but described in SUSv2 and POSIX.1-2001.

        Signal       Value     Action   Comment

--------------------------------------------------------------------
...
        SIGXFSZ     25,25,31    Core    File size limit exceeded (4.2BSD)

        Up to and including Linux 2.2, the default behavior for SIGSYS, 
SIGXCPU, SIGXFSZ, and (on architectures other than SPARC and MIPS) SIGBUS 
was to terminate the process (without a core dump).  (On some other Unix 
systems the default action for SIGXCPU and SIGXFSZ is to terminate the 
process without a core dump.)  Linux 2.4 conforms to the POSIX.1-2001 
requirements for these signals, terminating the process with a core dump.
""

On OS X 10.5, the manpages say the default action terminates without a 
core.

- Daniel