On Thursday 09 Feb 2006 16:01, 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.
Why use fputs which give you no indication of the type of error when the raw write does? B -- http://www.mailtrap.org.uk/ _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users