[minidlna] Fix foreground process and remove debug output

[quotschmacher]

would it be possible to make the debug output optional via a variable passed to the container? the enormous output of minidlna prevents my harddrive from spinning down.
and it seems that the debug output doesn't care about the configured log_level.

[vladgh]

How do you declare ‘log_level’ in your compose file?

On Fri, Aug 16, 2019 at 10:43 PM Sven ***@***.***> wrote: would it be possible to make the debug output optional via a variable passed to the container? the enormous output of minidlna prevents my harddrive from spinning down. and it seems that the debug output doesn't care about the configured log_level. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#88?email_source=notifications&email_token=AAC2LFNHTEJVTR6RKPTD533QE37PRA5CNFSM4IMMJEGKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HFXBPRA>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC2LFIY4JLJTMCSSSCSRO3QE37PRANCNFSM4IMMJEGA> .

-- — Vlad

[quotschmacher]

Not in the compose. It is a minidlna Option. You are starten minidlna with the '-d' Option and this should be optional

[vladgh]

Can you post here the command you use to start the container?

On Sat, Aug 17, 2019 at 9:30 AM Sven ***@***.***> wrote: Not in the compose. It is a minidlna Option. You are starten minidlna with the '-d' Option and this should be optional — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#88?email_source=notifications&email_token=AAC2LFJCY4NXLOYKYHQAF5LQE6LIRA5CNFSM4IMMJEGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4QEU6I#issuecomment-522209913>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC2LFNXGTG5WJ3PW55CYWLQE6LIRANCNFSM4IMMJEGA> .

-- — Vlad

[quotschmacher]

it's not about how i start the container. in your entrypoint.sh you call minidlna (hardcoded) with the '-d' parameter. this enables the debug-output which nearly floods the docker container log.

[vladgh]

Now I see what you mean. -d was used because it did not daemonize the process. But now that you mentioned it, I found a better way, with -S which will also keep the process in the foreground, but will listen to log_level (which is warn by default).
So thanks for bringing this up, I will update the image.