Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Add new files to the share after minidlna is started.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Add new files to the share after minidlna is started.
* What was the outcome of this action?
THe newly added files did not reflect on my DLNA client
* What outcome did you expect instead?
Newly added files should be sensed by minidlna and served to the DLNA client. Doing a force-reload does work.
Have you checked to make sure users are allowed to create enough inotify watches? This is a frequent minidlna issue when having more than just a few media files. It'd be nice to add a comment about this to minidlna.conf. See the Arch wiki: https://wiki.archlinux.org/index.php/MiniDLNA#Automatic_Media_DB_Update Regards, Florian
Have you checked to make sure users are allowed to create enough inotify watches? This is a frequent minidlna issue when having more than just a few media files. It'd be nice to add a comment about this to minidlna.conf. See the Arch wiki: https://wiki.archlinux.org/index.php/MiniDLNA#Automatic_Media_DB_Update Regards, Florian
From what i recollect i did. That was an ask in the config file itself. By the way I'm no more using minidlna. So can't provide any realtime information more s3nt fr0m a $martph0ne, excuse typ0s On May 13, 2014 8:24 PM, "Florian Will" <florian.will@gmail.com> wrote: Have you checked to make sure users are allowed to create enough inotify watches? This is a frequent minidlna issue when having more than just a few media files. It'd be nice to add a comment about this to minidlna.conf. See the Arch wiki: https://wiki.archlinux.org/index.php/MiniDLNA#Automatic_Media_DB_Update Regards, Florian
From what i recollect i did. That was an ask in the config file itself. By the way I'm no more using minidlna. So can't provide any realtime information more s3nt fr0m a $martph0ne, excuse typ0s On May 13, 2014 8:24 PM, "Florian Will" <florian.will@gmail.com> wrote: Have you checked to make sure users are allowed to create enough inotify watches? This is a frequent minidlna issue when having more than just a few media files. It'd be nice to add a comment about this to minidlna.conf. See the Arch wiki: https://wiki.archlinux.org/index.php/MiniDLNA#Automatic_Media_DB_Update Regards, Florian
There might be another way to fix this, as can be seen in the tracker package: http://anonscm.debian.org/cgit/collab-maint/tracker.git/tree/debian/30-tracker.conf Add a .conf to the package to increase the watches limit. Regards, Florian
Wed, 04 Mar 2015 19:38:15 +0100 Florian Will <florian.will@gmail.com> wrote: I think, that I'd better put instruction to README.Debian. It's not common to have over 8 thousand directories shared, so I think it's system administrator who should decide.
You have received a new fax. Please download attached fax document. Scanned at: Wed, 28 Oct 2015 13:13:31 +0300 Filesize: 235 Kb Scanned by: Jay Simon Fax name: task_00000886260.doc Pages number: 3 Scan duration: 19 seconds Scan quality: 200 DPI Thanks for using Interfax service!
I have this problem, too. IMHO minidlna should not require difficult system changes besides changing the default search path for music and video files, but it should work out of the box. If necessary, it should give inotify the boot and poll the search paths at boot time and once every hour. Regards Harri
This issue is now pretty much moot, since by default $ sysctl fs.inotify.max_user_watches fs.inotify.max_user_watches = 65536 and 64K "should be enough for anyone."