A handful of questions and a couple of documentation errors

[Robert Brenstein]

>on 1/12/04 5:15 AM, Ken Ray at kray at sonsothunder.com wrote:
>
>>>>  4) The log file that is maintained by Valentina Server during
>>>>  operation... does it have a maximum size it can reach? Or
>>>  do you only
>>>>  keep the last X amount of entries in the log file to keep it small?
>>>
>>>  As far as I know,
>>>
>>>  There is no any limits now.
>>>  Yes, Igor?
>>>
>>>  On each Vserver start, it re-write log file and start it again.
>>
>>  OK, so that means that if the server machine stay's "up" for a long
>>  time, we could get a large log file generated (depending on the verbose
>>  level), right Ruslan/Igor?
>
>Yes.
>
>Usually in deployment mode, verbose should be zero.
>
>And yes, I think we need add SIZE LIMIT on log, as this do other DBs
>

Overwriting log files is a bad idea in my book. For example, if there 
was a system crash and the server is launched automatically after 
reboot, then one can't check out the log file at all. This may be 
needed for client support aside from development.

Why don't you support log rollovers whenever the time or size limit 
is reached as many servers do? I mean that a user sets in the server 
config whether to expire logs by size (max file 1 mb, max file 2.2 
mb) or by time (every day at 00:05, every 3 days at 1 am, every 
saturday at 9 am, every 1st of the month at 00:01). At the roll time, 
the server puts a timestamp on the log file (that is renames it) and 
then starts a new one. This is quite easy to implement.

Robert Brenstein