On Sat, Aug 20, 2005 at 05:33:27PM -0700, [email protected] wrote:
> Another annoying problem is that once the system reaches this 2GB
> limit, then every process which exits will receive a signal,
> SIGXFSZ. This signal is generated because an attempt was made to
> write beyond the limit for the file descriptor. This signal makes
> it look like every process has exited due to a signal, when in fact,
> they have not.
Eeek.
> The solution is to add the O_LARGEFILE flag to the list of flags
> used to open the accounting file. The rest of the accounting
> support is already largefile safe.
That fixes the larger accounting file problem but it doesn't address
the fact that signals resulting writes to the accounting file are
delivered incorrectly.
We could still have issues if the accounting file as over quota for
example. Surely all accounting file writes should be insulated from
the processes involved?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |