On Saturday 11 Feb 2006 00:10, Kevin P. Fleming wrote: > Warren Burstein wrote: > > How about if it would set a global variable before each disk write so > > the SIGFSZ handler would know which file caused it? > > 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.
Well, you seem to have totally ignore what I said. Using fopen/fputs to ONLY append to a file, is quite frankly, stupid. Change it to open/write and you will be able to trap via the write return code and errno. 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
