Using server logs to automate podcast deletions
Posted: Tue Nov 03, 2009 4:45 am
Is anyone aware of a way to pull info on whether or not a file has been played through the logs TM Server keeps? My hope was to write a shell script that'd scan the log files and remove podcasts I'd already played. There were two problems I noticed:
1) The default log files are painfully verbose. A lot of (otherwise unknown) server actions in addition to files accessed
2) There is logging of media accessed, but it's not always transparent from the logs what was accessed on the file system. From my test cases, the logs utilize names derived from ID3 and other metadata (like the URLs seen in the web browser), not the name of the actual files
Ideally, there'd just be a log file of accessed media, using the actual file name rather than derived data. Can I modify the logging behavior to generate this? Or maybe someone else has already found a work around? Or am I out of luck?
My setup:
Twonky Media Server 5.0.68
OS: Debian 5
Thanks!
1) The default log files are painfully verbose. A lot of (otherwise unknown) server actions in addition to files accessed
2) There is logging of media accessed, but it's not always transparent from the logs what was accessed on the file system. From my test cases, the logs utilize names derived from ID3 and other metadata (like the URLs seen in the web browser), not the name of the actual files
Ideally, there'd just be a log file of accessed media, using the actual file name rather than derived data. Can I modify the logging behavior to generate this? Or maybe someone else has already found a work around? Or am I out of luck?
My setup:
Twonky Media Server 5.0.68
OS: Debian 5
Thanks!