aboutsummaryrefslogtreecommitdiff
path: root/multimedia/minidlna/files/minidlna.config
Commit message (Collapse)AuthorAge
* minidlna: update to latest masterRosen Penev2020-02-23
| | | | | | | | | | | | | | | | | | | | | | | Removed inactive maintainer. Cleaned up Makefile to remove old options. Switched to PKG_INSTALL for consistency. Added PKG_BUILD_PARALLEL for faster compilation. Fixed license info. Removed '' from enabled for consistency. Ran init script through shellcheck. Batched config file writes. Switched it to use procd. The -S parameter changes it to foreground. It stands for systemd. Added a sysctl tweak to get rid of warning. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* minidlna: create UUID in config if it is emptyAlberto Bursi2020-01-11
| | | | | | | | | 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: add static uuid in configAlberto Bursi2019-12-13
| | | | | | | | | | | | | | | | | | | | | | | 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>
* minidlna: run as an unprivileged userMaxim Storchak2019-03-10
| | | | | | | | | - 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>
* minidlna: add allow wide links optionJames Christopher Adduono2017-10-16
| | | | | | | | | | | | | | 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>
* Update minidlna to 1.1.3 versionmedaved2014-07-21
|
* first commitmedaved2014-07-15