"Extremely verbose" indeed - it can produce gigabytes of log data in a
single day. Before I applied the workaround below, it filled the root
disk of my home server system three times.
Unfortunately it looks like the version in Bullseye does not have the
"start_daemon" configuration file option.
As a workaround, you might want to create a
/etc/systemd/system/miniupnpd.service.d/override.conf file with the
following contents:
----cut here----
[Service]
Type=forking
ExecStart=
ExecStart=/usr/sbin/miniupnpd -f /etc/miniupnpd/miniupnpd.conf \
$MiniUPnPd_OTHER_OPTIONS
----cut here----
(Note: backslash denotes a line split because of email formatting
restriction.)
After creating the override file (and probably also the
miniupnpd.service.d directory to hold it), run "systemctl
daemon-reload", then "systemctl restart miniupnpd".
The use of "Type=forking" is not optimal, but that's probably best you
can do unless you're willing to rebuild the package from source.
