New beta/experimental OSD rendering resolution for HD300 ?

[drewg]

Originally Posted by TwistedMelon

It does keep more logging info. Except, "0" is the NEWEST log file. Followed by 1, 2, etc. In other words, the ordered numbered files represent the log events going backwards in time.

If you have 2 files, log and log.0, then log.0 is the oldest, and log is the most recent. Eg, log is the one that is still growing, and log.0 has been rotated and is static.

Note that when debug logging is enabled on the HD300, only one rotated log is kept by default. Eg:

tango3[~]# syslogd -h
<....>
        -S              Smaller logging output
        -s SIZE         Max size (KB) before rotate (default=200KB, 0=off)
        -b NUM          Number of rotated logs to keep (default=1, max=99, 0=purge)
<...>

tango3[~]# ps ax | grep syslog
  903 root       0:25 syslogd -S 
 1297 root       0:00 grep syslog

So on an hd300 at least, messages.0 will always be the oldest log file..

Drew

[drewg]

Originally Posted by _Demo_

Please try to latest 20101027-0 beta firmware and let me know if it fix your timeouts.

Thanks

_Demo_

My timeouts are fixed as well.

Thank you!!

Drew

[TwistedMelon]

Originally Posted by drewg

So on an hd300 at least, messages.0 will always be the oldest log file..

Sorry, I was talking specifically about the Sage log files. 0,1,2,3 by default. 0 the newest, 3 the oldest.

Always named in the format "sagetv_0.txt"