miniDLNA status

dodko · December 19, 2018, 8:53pm

LuCI Overview:
The miniDLNA service is not running.

mam zaskrtnute enable miniDLNA (miniDLNA settings)
v startupe je uvedene minidlna ako Enabled.

neviem co robim zle.
musi tam byt nieco specialne este nastavene?

dakujem

sammy_cda · December 19, 2018, 9:29pm

Yep. I had to enable it. Works great. Thanks!

peci1 · December 20, 2018, 8:59pm

github.com/openwrt/packages

minidlna: Wait for resources (network, disk) to be brought up

opened 11:59PM - 16 Jan 18 UTC

closed 11:38PM - 18 Aug 22 UTC

peci1

help wanted

Maintainer: @medaved Environment: TurrisOS (fork of OpenWRT, but minidlna is b…asically unchanged) Description: My system is probably specific by its slow network setup (probably due to the VDSL WAN, which somehow takes about a minute to connect). I'm only running minidlna on br-lan, but even this interfaces' startup is delayed by the WAN setup. And this slow setup started to show that minidlna is unable to start using the init scripts. When I run the init script manually after the router has booted, the minidlna daemon works as expected. So I expect that minidlna doesn't start during boot because the interface is not ready when the init script is run. Looking through the init script, there's no mention of waiting for the interface to show up. The question is: **should a wait for correct interface state be added to the init script?** Or, maybe as a better solution - **should the init script be changed to a `hotplug.d/iface` script?** I can imagine that if the network interface would not come up for some reason, the minidlna startup script should not block the start of the rest of init scripts.