better solution than using a static UUID by default

keep the default uuid empty then generate and save
a unique UUID on first start of minidlna service.

Signed-off-by: Alberto Bursi <bobafetthotmail@gmail.com>

minidlna uses UUID to uniquely identify the media server
by default, if the "uuid" option is not specified in
its setting file it will try to autogenerate it by
reading MAC address.

This seems to fail on some devices resulting in random
UUID on reboot, and this causes confusion and issues as
for clients this is a new server and must be added to
the list.
In OpenWrt there are also devices where the system can't
read the true MAC address and it is therefore randomized
on reboot.

So, add a static UUID in the settings file.
Since each mindlna server should have a different UUID,
if the user has more than one OpenWrt device with
minidlna, he should change the UUID of the
additional devices.

Signed-off-by: Alberto Bursi <bobafetthotmail@gmail.com>

- run as an unprivileged user by default
- move generated config to /var/run (/tmp/run in fact)
- disable service until it's configured: there is no way to reliably guess
  where files to be shared are located

Signed-off-by: Maxim Storchak <m.storchak@gmail.com>

Some clients do not close connections properly or do not keep
it alive, so each time the connection times out a corresponding
log entry is written into a log. These messages may spam the log
really hard.
This may be an issue if log is placed on internal flash - it may
prematurely wear a flash chip. This also prevents hdd from spinning
down if the log is located on hdd and the dlna capable tv is online.

Set the log level to "error" by default.

MAN:
Set this to change the verbosity of the information that is logged
each  section can use a different level: off, fatal, error, warn,
info, or debug
Example
log_level=general,artwork,database,inotify,scanner,metadata,http,ssdp,tivo=warn

Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>

Some users might create a minidlna root with symlinks
to shared locations. While this could potentially create
a vulnerability, the option should be available to allow
users to do this should they choose to.

wide_links=no : (default) no content served + error message
 [timestamp] upnphttp.c:1366: error: Rejecting wide link X

wide_links=yes : content served, no error messages

Signed-off-by: James Christopher Adduono <jc@adduono.com>

Signed-off-by: Ted Hess <thess@kitschensync.net>