Re: [vdr] option parsing for --log still broken

On 17.11.20 12:17, Harald Milz wrote: Hi Klaus and all, it appears that option parsing for the --log option is still broken, as described in this thread: https://www.vdr-portal.de/forum/index.php?thread/108924-gel%C3%B6st-logging-von-yavdr-in-separaten-logfiles-anstelle-des-syslog-und-probleme/

Re: [vdr] Many "Tuning timeout" messages and signal disruptions

I'd either use bare metal or maybe a container (LXC, not sure sure about docker) as that's as near as bare metal with few encumbrances. Why ? I've always used bare metal, and it seems VDR is working quite close to the hardware, adding layers adds complexity. But the other thing is that that s

[vdr] option parsing for --log still broken

Hi Klaus and all, it appears that option parsing for the --log option is still broken, as described in this thread: https://www.vdr-portal.de/forum/index.php?thread/108924-gel%C3%B6st-logging-von-yavdr-in-separaten-logfiles-anstelle-des-syslog-und-probleme/ Short version: vdr stops parsing the