From: Richard B. <ri...@bu...> - 2007-12-05 02:42:58
|
There are several challenges to be resolved in the logging. First and foremost; the logging code is so low level that I cannot guarantee access to the various conf variables so adding switches to the logging is not likely. Second, there are two logging libraries that need reworking, however, I wonder if a good decorator pattern would suffice. Finally, I need to review and make recommendations for the implementation of logrotate including sample conf file. The big questions... a) what do we do when the platfor (Windows) does not have a real logrotate like unix? b) should this actually be a ./configure param instead of runtime in order to select the rotate style. -Richard PS: It's important to note that logrotate can be used with the current implementation. The SIZE in the logrotate conf needs to be smaller than the yaws log filesize limit. Of course you can always increase the number from 1M to 10M in yaws. Then set the logrotate size to 9M. It's important to note that this may not always be effective. It depends on a number of factors. In the meantime I'm going to review the various requests in the previous list and then implement the code. It should not take more than a few hours if I can schedule my time. Opinions please! |
From: Richard B. <ri...@bu...> - 2007-12-05 03:16:59
|
Here is my proposal based on the current implementation and lack of access to the config and the fact that there are two logging modules which may or may not be implemented.... and the internal usage of the State record which contains a second reference to the log_wrap_size. More importantly since yaws is compiled before executed. To enable wrapping with the default 1M size limit: ./configure <with your other params> to enable wrapping at 100K instead of 100M ./configure --log_wrap_size 100000 <with your other params> to disable wrapping ./configure --log_wrap_size 0 <with your other params> The following is logrotate.conf snippet. (WARNING: Not tested) "/var/log/yaws/*.access" { rotate 5 size=100k postrotate yaws --hup -I <id> endscript } Comments please. On Dec 4, 2007, at 9:42 PM, Richard Bucker wrote: There are several challenges to be resolved in the logging. First and foremost; the logging code is so low level that I cannot guarantee access to the various conf variables so adding switches to the logging is not likely. Second, there are two logging libraries that need reworking, however, I wonder if a good decorator pattern would suffice. Finally, I need to review and make recommendations for the implementation of logrotate including sample conf file. The big questions... a) what do we do when the platfor (Windows) does not have a real logrotate like unix? b) should this actually be a ./configure param instead of runtime in order to select the rotate style. -Richard PS: It's important to note that logrotate can be used with the current implementation. The SIZE in the logrotate conf needs to be smaller than the yaws log filesize limit. Of course you can always increase the number from 1M to 10M in yaws. Then set the logrotate size to 9M. It's important to note that this may not always be effective. It depends on a number of factors. In the meantime I'm going to review the various requests in the previous list and then implement the code. It should not take more than a few hours if I can schedule my time. Opinions please! |
From: Richard B. <ri...@bu...> - 2007-12-05 03:24:30
|
Sorry to be a pest but it appears that the log_wrap_size is configurable. When it's ZERO (0) no wrapping will take place. Forget build time. On Dec 4, 2007, at 10:16 PM, Richard Bucker wrote: Here is my proposal based on the current implementation and lack of access to the config and the fact that there are two logging modules which may or may not be implemented.... and the internal usage of the State record which contains a second reference to the log_wrap_size. More importantly since yaws is compiled before executed. To enable wrapping with the default 1M size limit: ./configure <with your other params> to enable wrapping at 100K instead of 100M ./configure --log_wrap_size 100000 <with your other params> to disable wrapping ./configure --log_wrap_size 0 <with your other params> The following is logrotate.conf snippet. (WARNING: Not tested) "/var/log/yaws/*.access" { rotate 5 size=100k postrotate yaws --hup -I <id> endscript } Comments please. On Dec 4, 2007, at 9:42 PM, Richard Bucker wrote: There are several challenges to be resolved in the logging. First and foremost; the logging code is so low level that I cannot guarantee access to the various conf variables so adding switches to the logging is not likely. Second, there are two logging libraries that need reworking, however, I wonder if a good decorator pattern would suffice. Finally, I need to review and make recommendations for the implementation of logrotate including sample conf file. The big questions... a) what do we do when the platfor (Windows) does not have a real logrotate like unix? b) should this actually be a ./configure param instead of runtime in order to select the rotate style. -Richard PS: It's important to note that logrotate can be used with the current implementation. The SIZE in the logrotate conf needs to be smaller than the yaws log filesize limit. Of course you can always increase the number from 1M to 10M in yaws. Then set the logrotate size to 9M. It's important to note that this may not always be effective. It depends on a number of factors. In the meantime I'm going to review the various requests in the previous list and then implement the code. It should not take more than a few hours if I can schedule my time. Opinions please! |
From: <kl...@ta...> - 2007-12-05 09:31:24
|
Richard Bucker wrote: > > a) what do we do when the platfor (Windows) does not have a real > logrotate like unix? Fallback to the method used today. > b) should this actually be a ./configure param instead of runtime in > order to select the rotate style. > Yes, config param and I think the deafult should be the current scheme. Most people don't even know what a logrotator is even less how they work. This would typically only be an issue for people deploying yaws in production environments and to distro packagers. /klacke -- Claes Wikstrom -- Caps lock is nowhere and http://www.tail-f.com -- everything is under control cellphone: +46 70 2097763 |