miniDLNA doesn't seem to update database autonomously

miniDLNA works perfectly for me and lets me access all my media on Android devices, XBMC, internet radio, and a sony bluray player as well (as long as the device has the right decoders).

But, for some reason, it doesn't seem to add new files which I add to its folders.

Now if found this post

In summary, the most reliable way to have MiniDLNA rescan all media files is by issuing the following set of commands:

$ sudo minidlna -R
$ sudo service minidlna restart

However, every so often MiniDLNA will be running on a server. Here is a client-side script to request a rescan on such a server:

#!/bin/bash
ssh -t server.on.lan 'sudo minidlna -R && sudo service minidlna restart'

and

AzP already provided most of the information, but some of it is incorrect.
First of all, there is no such option inotify_interval. The only option that exists is notify_interval and has nothing to do with inotify.
So to clarify, notify_interval controls how frequently the (mini)dlna server announces itself in the network. The default value of 895 means it will announce itself about once every 15 minutes, meaning clients will need at most 15 minutes to find the server. I personally use 1-5 minutes depending on client volatility in the network.
In terms of getting minidlna to find files that have been added, there are two options:

• The first is equivalent to removing the file files.db and consists in restarting minidlna while passing the -R argument, which forces a full rescan.

• The second is to rely on inotify events by setting inotify=yes and restarting minidlna. If inotify is set to =no, the only option to update the file database is the forced full rescan.

Additionally, in order to have inotify working, the file-system must support inotify events, which is not the case in most remote file-systems. If you have minidlna running over NFS it will not see any inotify events because these are generated on the server side and not on the client.

Finally, even if inotify is working and is supported by the file-system, the user under which minidlna is running must be able to read the file, otherwise it will not be able to retrieve necessary metadata. In this case, the logfile (usually /var/log/minidlna.log) should contain useful information.

 on http://stackoverflow.com/questions/5180409/why-minidlna-not-refreshing-database