Package: minidlna
Version: 1.3.0+dfsg-2+deb11u1
Hello,
this report is based on that German forum post where someone still
helped me to solve the problem and also analyzed the root of the
problem.
https://debianforum.de/forum/viewtopic.php?p=1307710#p1307710
I'm using multiple instances of minidlna on the same machine via systemd
Template-Units. This worked like a charm on Debian 10 (and maybe 9).
In Debian 10 (Buster) minidlna doesn't used a log-file when the option
-S was used and just logged to stdout. See [1] and [2].
Upstream did some modifications [3] but Debian patched [4] because of
unknown reasons. Upstream still don't use a log-file. But Debian use a
log-file when -S is used and set the log-folder to a default-value [5]
and the log-filename is hardcoded [6]. That makes it hard to use
multiple instances or make the need of unusual workarounds. Currently I
set the log-folder not via Template-Unit but explicite for each Unit in
the .conf file.
I don't know a solution or a good way to solve this. I don't take care
much about log files in context of minidlna. I just wanted to report it.
[1] --
<https://sources.debian.org/src/minidlna/1.2.1%2Bdfsg-2%2Bdeb10u2/log.c/#L126-L127>
[2] --
<https://sources.debian.org/src/minidlna/1.2.1%2Bdfsg-2%2Bdeb10u2/minidlna.c/#L942-L967>
[3] --
<https://salsa.debian.org/debian/minidlna/-/blob/debian/1.3.0+dfsg-2/minidlna.c#L1014-1018>
[4] --
<https://salsa.debian.org/debian/minidlna/-/blob/debian/1.3.0+dfsg-2/debian/patches/09-do-not-disable-logs-with-systemd.patch>
[5] --
<https://sources.debian.org/src/minidlna/1.3.0%2Bdfsg-2%2Bdeb11u1/minidlna.c/#L821-L822>
[6] --
<https://sources.debian.org/src/minidlna/1.3.0%2Bdfsg-2%2Bdeb11u1/log.c/#L141>
