[Asterisk-Users] asterisk logger - urgent!!!

[Warren Burstein]

Kevin P. Fleming wrote:
> Dov Bigio wrote:
>   
>> Any way, if any developers are reading this, I don't think that rotating
>> asterisk logs is the best way to handle this problem!
>> Maybe a more user-friendly message could be logged, infoming which file
>> reached the 2.0GB.
>>     
>
> Unfortunately when we receive SIGFSZ from the kernel, we have no way to
> know which file caused it. The assumption in Asterisk is that the only
> files we write to that will ever reach that size are log files. If any
> other file does, there will be trouble, as you have seen.
>   
How about if it would set a global variable before each disk write so 
the SIGFSZ handler would know which file caused it?