From: Yariv S. <yar...@gm...> - 2007-11-28 06:16:36
|
Hi, I'm trying to figure out how to make Yaws preserve all traffic logs. As I understand it, every time a Yaws log reaches the log wrap size configuration value, Yaws copies the current log file to [filename].old and then truncates the current log file and resumes logging at the beginning of the file. The problem I'm facing -- if I understand Yaws's behavior correctly -- is that the previous [filename].old gets overwritten and the previous logging data is lost. What I'd like Yaws to do is instead of overwriting old data, to archive it in gzipped files so it can be analyzed later. Is this possible or am I off track? Thanks, Yariv |
From: Claes W. <kl...@ta...> - 2007-11-28 07:39:38
|
Yariv Sadan wrote: > Hi, > > I'm trying to figure out how to make Yaws preserve all traffic logs. > As I understand it, every time a Yaws log reaches the log wrap size > configuration value, Yaws copies the current log file to > [filename].old and then truncates the current log file and resumes > logging at the beginning of the file. The problem I'm facing -- if I > understand Yaws's behavior correctly -- is that the previous > [filename].old gets overwritten and the previous logging data is lost. > What I'd like Yaws to do is instead of overwriting old data, to > archive it in gzipped files so it can be analyzed later. Is this > possible or am I off track? > slightly off track, unless the code is buggy, yaws is archiving now, but with just one old generation. What is the right fix here IMHO is to change the yaws logging behaviour into a much simpler version which can be more easily integrated into normal UNIX logrotate scenarios. Let the right tool do the job. All logging code needs to be removed and then yaws just has to close and reopen the logfiles when told to. That is the requirement logrotator tools have. -klacke |
From: Lev W. <vl...@li...> - 2007-11-28 07:58:06
|
Claes, we have this requirement as well. Would you please consider adding it sometime? Claes Wikstrom wrote: > Yariv Sadan wrote: >> Hi, >> >> I'm trying to figure out how to make Yaws preserve all traffic logs. >> As I understand it, every time a Yaws log reaches the log wrap size >> configuration value, Yaws copies the current log file to >> [filename].old and then truncates the current log file and resumes >> logging at the beginning of the file. The problem I'm facing -- if I >> understand Yaws's behavior correctly -- is that the previous >> [filename].old gets overwritten and the previous logging data is lost. >> What I'd like Yaws to do is instead of overwriting old data, to >> archive it in gzipped files so it can be analyzed later. Is this >> possible or am I off track? >> > > slightly off track, unless the code is buggy, yaws is archiving > now, but with just one old generation. > > What is the right fix here IMHO is to change the yaws > logging behaviour into a much simpler version which can > be more easily integrated into normal UNIX logrotate > scenarios. > > Let the right tool do the job. > > All logging code needs to be removed and then yaws just > has to close and reopen the logfiles when told to. That is > the requirement logrotator tools have. > > -klacke > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list |
From: <kl...@ta...> - 2007-11-28 16:13:51
|
Lev Walkin wrote: > > Claes, we have this requirement as well. Would you please consider > adding it sometime? > A volunteer just arrived, richard bucker volunteered to write this code. /klacke -- Claes Wikstrom -- Caps lock is nowhere and http://www.tail-f.com -- everything is under control cellphone: +46 70 2097763 |
From: Yariv S. <yar...@gm...> - 2007-12-05 01:23:28
|
Great... please let us know when it's done. > > A volunteer just arrived, richard bucker volunteered > to write this code. > > > /klacke > > -- > Claes Wikstrom -- Caps lock is nowhere and > http://www.tail-f.com -- everything is under control > cellphone: +46 70 2097763 > |