On Sunday 12 Feb 2006 01:04, Kevin P. Fleming wrote:
[...]
(and by 'you' I don't mean you specifically, Michael, I am referring to
those in this thread who think we should change the code used to write
to every file we write to in Asterisk)
I assume you are referring to me. I did not say that.
On Sunday 12 Feb 2006 10:57, Bob Goddard wrote:
On Sunday 12 Feb 2006 01:04, Kevin P. Fleming wrote:
[...]
(and by 'you' I don't mean you specifically, Michael, I am referring to
those in this thread who think we should change the code used to write
to every file we write to in Asterisk)
I agree that systems should be well-adminstered, I also prefer
programs that don't run amok even when there are lapses in
administration.
Since detecting which file caused the SIGFSZ is impractical, how about
if we do this.
a) don't rotate logs on SIGFSZ if it's done it recently.
b) when it
Warren Burstein wrote:
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)
And there's the important point: any other files that are written to.
Asterisk writes to
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
Bob Goddard wrote:
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.
Patches to fix bugs are most welcome. Given that these files are written
using fprintf (because they are using
: [Asterisk-Users] asterisk logger - urgent!!!
Bob Goddard wrote:
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.
Patches to fix bugs are most welcome. Given that these files are written
Michael Collins wrote:
I am curious to know if putting the output into a char array with
sprintf() (to preserve the output formatting) and then writing it with
write(). How much additional overhead would this take? Hard to know
without trying it.
Please... if you don't have the skills to
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
On Thu, Feb 09, 2006 at 10:56:18AM -0200, Dov Bigio wrote:
Hi,
Since yesterday my Asterisk 1.2.3 is displaying the following message every
few seconds
Asterisk Event Logger restarted
Rotated Logs Per SIGXFSZ (Exceeded file size limit)
This causes my log files (verbose, queue_log) to
PROTECTED]; Asterisk Users Mailing List -
Non-Commercial Discussion asterisk-users@lists.digium.com
Sent: Thursday, February 09, 2006 11:42 AM
Subject: Re: [Asterisk-Users] asterisk logger - urgent!!!
On Thu, Feb 09, 2006 at 10:56:18AM -0200, Dov Bigio wrote:
Hi,
Since yesterday my Asterisk 1.2.3
On Thu, Feb 09, 2006 at 11:56:02AM -0200, Dov Bigio wrote:
Hi Tzafrir,
The problem was the file Master.csv that had reached 2.0GB.
I am writing a cron script to backup this file periodically and prevent this
from happening.
Any way, if any developers are reading this, I don't think that
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
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.
: Thursday, February 09, 2006 2:01 PM
Subject: Re: [Asterisk-Users] asterisk logger - urgent!!!
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
Dov Bigio wrote:
Is there a way to rotate CDR CSV files via Asterisk, or should I handle this
outside Asterisk?
As another reply already mentioned, no and yes :-)
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
@lists.digium.com
Sent: Thursday, February 09, 2006 2:01 PM
Subject: Re: [Asterisk-Users] asterisk logger - urgent!!!
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
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
18 matches
Mail list logo
