Open GoogleCodeExporter opened 9 years ago
While there is no documentation regarding the logs and the rotation mechanism,
the source code may help a bit, I guess. I'd suggest to look at
apt_log_file_dump() function, it consists of a few lines only.
http://code.google.com/p/unimrcp/source/browse/trunk/libs/apr-toolkit/src/apt_lo
g.c#556
The main idea is to split one big log file into N small ones. So, instead of
dumping all the log entries to the storage, only current log file is
dumped/saved. The idea originally came from one of the UniMRCP users and it
makes sense to me.
Anyway, if you have more questions, ideas or thoughts on how to improve the
routine, please feel free to discuss them on the discussion group.
http://groups.google.com/group/UniMRCP
If you come up with a patch or meet an issue, please feel free to use the issue
tracker then.
Original comment by achalo...@gmail.com
on 14 Jan 2011 at 4:30
The biggest issue I have with the default settings is that it does a log
rotation for every 8M. Ok I can live with that to an extend and it is somethng
that I can change and recompile. The worst offender is MAX_LOG_FILE_COUNT which
is OK as long as UniMRCP is not heavily used. As soon as it handles a few
thousand TTS or others with debug ON, we loose the initial logs. Keeping logs
is vital for debugging production issues.
I really think we should add syslog support into UniMRCP. Who doesnt have basic
syslog on their systems these days, especially in production; unless there is a
real reason to not to go down syslog route.
Original comment by dcko...@gmail.com
on 14 Jan 2011 at 10:06
Sounds good. If you could enhance the UniMRCP logger to support syslog as well,
I'd be certainly glad to apply your modifications.
Original comment by achalo...@gmail.com
on 15 Jan 2011 at 5:11
Original comment by achalo...@gmail.com
on 7 Mar 2013 at 8:53
Original issue reported on code.google.com by
dcko...@gmail.com
on 16 Dec 2010 at 5:12