[packman] systemd unit file ignores minidlna default configuration

Bob Williams usenet at karmasailing.uk
Tue Jan 2 20:51:13 CET 2018

My system is openSUSE Leap 42.3, and I am using the version of minidlna from the packman repository.

For some time I have been successfully running a minidlna server which streams music to a Bose Soundtouch device over WiFi. However, it stopped working a few weeks ago, and the SoundTouch device could only find an empty folder.

After several re-writes of /etc/minidlna.conf without success, and searching for other versions of minidlna.conf in non-default locations, I finally tracked the culprit down to /usr/lib/systemd/system/minidlna.service which contained the following:

Description=MiniDLNA UPnP-A/V and DLNA media server
After=var-run.mount nss-lookup.target network.target remote-fs.target

ExecStart=/usr/sbin/minidlnad $RESCAN -P /var/run/minidlnad.pid -f /var/lib/minidlna/minidlna.conf [0]


So the unit file was forcing minidlna to use the configuration file in /var/lib/minidlna/minidlna.conf rather than the default /etc/minidlna.conf! /var/lib/minidlna/minidlna.conf pointed to media_dir=/mnt and was recreated at start-up, so even editing the media_dir= line didn't work. Changing the last line in the [Service] stanza to include "-f /etc/minidlna.conf" got things working again - and just in time for Christmas. ;-)

I have no idea how this got changed, but I wonder if anyone else has come across anything similar?


Bob Williams
   System:  Linux 4.4.103-36-default
   Distro:  openSUSE 42.3 (x86_64)
   Desktop: KDE Frameworks: 5.32.0, Qt: 5.6.2 and Plasma: 5.8.7

More information about the Packman mailing list