[Bug?]Logger->Keep maximum of X files
Moderators: white, Hacker, petermad, Stefan2
[Bug?]Logger->Keep maximum of X files
I'm not sure if it should be called a bug, but this option doesn't behave the way I wanted it to and I miss some files this way.
How does it work? Creates X files, then stops logging. No warning, nothing.
When I set it, I thought that it will automatically delete the oldest ones, not turn logging off.
How does it work? Creates X files, then stops logging. No warning, nothing.
When I set it, I thought that it will automatically delete the oldest ones, not turn logging off.
-
- Senior Member
- Posts: 228
- Joined: 2006-02-04, 13:02 UTC
In my case it works like you (and me) expect. What options are used in addition? In my case I use a fixed path (i.e. C:\TEMP instead of %temp% - maybe %temp% isn't set like your expectations?) and "Every day after midnight".
"Since there are many things which have never happened and never will happen,
and which nevertheless are clearly conceivable, and imply no contradiction,
how can one say they are absolutely impossible?" Leibniz
and which nevertheless are clearly conceivable, and imply no contradiction,
how can one say they are absolutely impossible?" Leibniz
-
- Senior Member
- Posts: 228
- Joined: 2006-02-04, 13:02 UTC
My options
Log file: C:\TEMP\totalcmd.log
Logging all events except "File system plugins"
Every day after midnight.
Only 10 copies.
Maybe playing with the differences between your and my options will be dectected a cause?
Log file: C:\TEMP\totalcmd.log
Logging all events except "File system plugins"
Every day after midnight.
Only 10 copies.
Maybe playing with the differences between your and my options will be dectected a cause?
"Since there are many things which have never happened and never will happen,
and which nevertheless are clearly conceivable, and imply no contradiction,
how can one say they are absolutely impossible?" Leibniz
and which nevertheless are clearly conceivable, and imply no contradiction,
how can one say they are absolutely impossible?" Leibniz
Yep, it seems that's the problem, thanks. When I moved the TC.date.logs from the logs folder, TC renamed TC.log to TC.20071219.log. And there was a log with the same name moved..and I'm sure I didn't make it manually.
The moved log is pretty short..
Notice that program end is not there. Crash?
Let's take a look into the second one..
Started in 2003. So it was probably a crash with BIOS reset. Date changed, so TC renamed the "old" ( future? ) TC.log.
After starting TC I adjusted date. Why didn't TC rename the 2003 log? (bug?)
Anyway, when the day passed, it couldn't rename TC.log->TC.20071219.log because it was there already.
I suggest changing this behaviour. Maybe TC.20071219_2.log?
The moved log is pretty short..
Code: Select all
2007-12-19 11:21:09: Program start (1/M)
2007-12-19 11:35:49: Delete: E:\projects\ForceDel\aa
Let's take a look into the second one..
Code: Select all
2003-01-01 00:03:33: Program start (1/M)
2007-12-19 20:36:01: NewFolder: D:\TC\Tools\Media\VIDEO\RealAlternative\Media Player Classic\Codecs\
(...)
After starting TC I adjusted date. Why didn't TC rename the 2003 log? (bug?)
Anyway, when the day passed, it couldn't rename TC.log->TC.20071219.log because it was there already.
I suggest changing this behaviour. Maybe TC.20071219_2.log?
- ghisler(Author)
- Site Admin
- Posts: 48199
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact: