<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I agree that systems should be well-adminstered, I also prefer
programs that don't run amok even when there are lapses in
administration.<br>
<br>
Since detecting which file caused the SIGFSZ is impractical, how about
if we do this.<br>
a) don't rotate logs on SIGFSZ if it's done it recently.<br>
b) when it does rotate files on SIGFSZ,. it should rotate the csv file,
too, and any other files that are written to (maybe only of they are
larger than the file size limit)<br>
<br>
Kevin P. Fleming wrote:
<blockquote cite="mid43ED2B5C.7010408@digium.com" type="cite">
<pre wrap="">Warren Burstein wrote:
</pre>
<blockquote type="cite">
<pre wrap="">How about if it would set a global variable before each disk write so
the SIGFSZ handler would know which file caused it?
</pre>
</blockquote>
<pre wrap=""><!---->
Ha!
Signals are asynchronous. This global variable would to be
lock-protected, would require copying (possibly long) paths for every
write, and would not necessarily be correct when the signal arrived.
Sorry, this is not a solution. There is no solution, other than paying
attention to your server and making sure that files don't get
ridiculously large.
</pre>
</blockquote>
</body>
</html>