minidlna - change of loglevel / rescan of library

    • OMV 2.x
    • minidlna - change of loglevel / rescan of library

      Hi everybody, :)

      i found out about a somehow weird issue in minidlna. Is this how it is intended to work?



      When i change the loglevel in minidlna (i just tried out what information i get on each level), after that omv makes you to save your changes. After that, minidlna starts to rescan the whole library again. This takes hours with a big library.

      So my question is if this can be avoided somehow, to rescan after change of loglevel?

      Another question about the loglevel in minidlna: Can anybody tell me which loglevel to set, so i only see inotify messages and status messages, e,g scanning library complete or streaming to ...

      I was not able to find a suitable level.

      thank you so much.

      gkhar2
    • gkhar2 wrote:

      So my question is if this can be avoided somehow, to rescan after change of loglevel?
      Nope. You have to restart minidlna to change the loglevel and minidlna rescans when it starts. Why would you change the log level once you have it set?


      gkhar2 wrote:

      Can anybody tell me which loglevel to set, so i only see inotify messages and status messages, e,g
      If you can't find a level that only does what you want, then it must not exist. The only possible values are the ones listed in the plugin. Error is what I would use but I don't use minidlna anymore and never looked at the logging unless I had a problem (which was never).
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!