vServer log options

[Ivan Smahin]

Hello Danny,

Tuesday, March 2, 2010, 1:28:52 PM, you wrote:

> Hi Ivan,

> I don't think this is a good idea...
> Syslog rotates, so that means, at certain point you will start
> losing info (advantage is that the file has a maximum size...)
> But I have gone way back in logs sometimes to find a problem...

What about croned tasks for syslog maintenance?
I believe it is possible and very efficient way to keep it in order.


> What I would like, is to see that the logfile gets zipped at
> certain size, and a new one is started.
> This would keep the size of a log file usable, and we wouldn't lose any info.

Look, currently we have two ways which seems to be redundant.
No  much sense to have own logging approach (at least for server) -
thinking  of where to store the logs, its sizes, keep it in order with
zipping and so on. It is not easy and error-free way.
And it should be really convincing arguments to keep it both.

> Also, talking about this topic, in the log file, there is never a date mentioned for the message.
> What I mean are messages like this:

> 12:22:17.421120 (3024284560): (26) I_SqlDatabase 'demo_core_bb.vdb'
> SqlQuery 'SELECT objptr_orgstatus->listvalue AS org_status FROM
> tbl_organisations WHERE RecID = 1'.

->> no date mentioned

Good point - I guess you may see a whole date in syslog for any event.
So even time as part of log message is redundant for syslog.


-- 
Best regards,
Ivan Smahin 
Senior Software Engineer
Paradigma Software, Inc
Valentina - The Ultra-Fast Database
http://www.valentina-db.com