Re: [OpenSIPStack] Problem with OnOutgoingCallConnected
Brought to you by:
joegenbaclor
From: Ilian J. C. P. <ip...@so...> - 2007-07-17 08:17:59
|
Hi, tomach wrote: > Or how to send logs to syslog? Have You consider such a solution? For syslog you can do this: Logger::SetDefaultLevel( 5 ); static unsigned int options = LogDateAndTime | LogThread | LogAppendToFile; Logger::SetDefaultLogStream( new LoggingSystemLogStream( "ATLSIP", PIPSocket::Address("127.0.0.1"), PIPSocket::Address("127.0.0.1"), 514, 0, options ) ); > How do You cope with big log files finallly if You do not send them to syslog? I belive that after several days of working logs files can be really huge? > Typically *for* ATLSIP, we really not need to store all the logs. If a bug/problem is found, you would want the logs only for that scenario. So storing the logs per application runtime shouldn't hurt. Of course, there is no problem if you prefer to keep logs for a longer period. You'll just have to implement your own housekeeping. Regards, Ilian > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |