vServer log options

[Danny Lewkin]

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 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.

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

Just my 5 cents,

Greetz,

Danny





On 02 Mar 2010, at 12:18, Ivan Smahin wrote:

> Hello Valentina,
> 
>  What do you think of following idea?
> 
>  Currently there are 3 options of vServer logging:
> 
>  LogToConsole=1;                  Enables logging to the console.
>  LogToFile=1;                     Enables logging to the file.
>  LogToSysLog=1;                   Enables logging to the syslog.
> 
>  LogToConsole  seems to be helpful in order to see server activity in
>  case of running vServer in console.
> 
>  LogToSysLog  seems to be a right place to log - it could be managed
>  with a lot of tools (including system ones).
> 
>  We  are  going  to consider LogToFile as deprecated feature and stop
>  thinking   of  improvements  in  this  area.  Because  you  may  use
>  LogToSysLog facilities.
> 
> -- 
> Best regards,
> Ivan Smahin 
> Senior Software Engineer
> Paradigma Software, Inc
> Valentina - The Ultra-Fast Database
> http://www.valentina-db.com
> 
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina