Am 28.05.2012 19:30, schrieb Tommi Mäkitalo: >> Thanks, level configuration works. >> It seems everything goes to the<errorLog/>, what is the<accessLog/> for? >> >>> Rotating logs is not implemented. But it is a good idea. It should be >>> implemented. I will look at it also. >> Rotating can be done by the OS (e.g. placing a file in /etc/logrotate.d/), >> what's unexpected is that tntnet now resets (overwrites) the logs. >> > Of course can rotating be done by the OS. But if tntnet does it, tntnet > do not need to be restarted. It might be a cleaner solution. > > Here everything goes into the accessLog. But errorLog is unused. It > looks like it was never used. I will remove it. And accessLog is not > truncated. It works here like before and like it should work. > > Tommi Not quite true. "errorLog" is used for stderr. Stderr is redirected to errorLog, so if a application writed to std::cerr, it is written into errorLog. But this happens only when tntnet is started in daemon mode. And as I read in the code, it is really truncated. But that is nothing new. It is just a bug, which I will fix.
Tommi ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
