-----BEGIN PGP SIGNED MESSAGE-----
Am 18.01.2015 15:11, schrieb Manuel Reimer:
> On 01/18/2015 02:43 PM, Joerg Bornkessel wrote:
>>> - VDR now reads command line options from *.conf files in
>>> /etc/vdr/conf.d (thanks to Lars Hanisch). See vdr.1 and vdr.5
>>> for details.
>> Is there an example what exactly can we do with this? The
>> Manpage's give there very small information :( Lars?
> Have a look at the vdr4arch repository:
> We already used this feature using the patch created by Lars.
> This new feature is especially useful when using systemd or other
> event driven init systems. It now no longer is required to
> "somehow" construct a command line. Just start VDR
Oh Oh, systemd crap...
> vdr4arch places the plugin config files to /etc/vdr/conf.available
> first. It's the user's job to create a symlink to /etc/vdr/conf.d
> to enable the plugin or delete the symlink to disable a plugin.
this looks like, as has the user a lot of activity to do
in my opinion, prevent the end user from a lot of editing some files
or symlinking etc.
anyway, systemd is not my working place and i will see what ideas
comes from Lucian M. He is the manager of the systemd crap part in the
Thx for your reply
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: added by hd_bru...@gentoo.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
vdr mailing list