Hi Robie, I really appreciate your response. I subscribed you because "apt changelog" in my ubuntu 16.04 system shows you were the last person to update this package, so I thought you are the maintainer. The bug you referenced is not the same (that bug is about mediatomb writing to the same logfile even after it is rotated to .1 etc)
The bug I am noticing is different: In ubuntu, mediatomb's logrotate config references "/var/log/mediatomb.log" but the startup script references "/var/log/mediatomb" so it does not get rotated at all. All that is needed is to make them consistent by changing one of these 2 files. Having said that, debian bug 633803 seems to affect Ubuntu as well, so there are 2 things to be fixed here. Thanks for pointing out there is a fork (gerbera) https://gerbera.io/ I am noticing even http://mediatomb.cc/ says development stopped and people should check out gerbera. So I guess this is not worth fixing in mediatomb. To anyone interested, here is the workaround to stop mediatomb from writing to the same logfile forever: Edit /etc/logrotate.d/mediatomb and change: "/var/log/mediatomb.log" to: "/var/log/mediatomb" and "invoke-rc.d mediatomb reload" to: "invoke-rc.d mediatomb restart" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/488318 Title: Excessive Log Files To manage notifications about this bug go to: https://bugs.launchpad.net/mediatomb/+bug/488318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
