headers
Paul Menzel | 27 Jun 2012 11:48
Picon

Please share your systemd (Upstart) service file

Dear VDR folks,

looking around for systemd service files I found three examples. One
from OpenBricks [1],

    [Unit]
    Description=Video Disk Recorder
    After=lircd.service pvr.service
    ConditionPathExists=/run/geexbox/pvr/vdr

    [Service]
    ExecStart=/usr/bin/runvdr
    Restart=always

    [Install]
    WantedBy=multi-user.target

one from a VDR-Portal forum post [2]

        [Unit]
        Description=Video Disk Recorder
        After=lircd.service

        [Service]
        ExecStart=/usr/local/src/VDR/vdr --lirc=/run/lirc/lircd -s /usr/local/bin/vdr-shutdown.sh -v
/var/lib/vdr/video -w 90 -Plive -Pstreamdev-server -P 'epgsearch
--config=/etc/vdr/plugins/epgsearch' -P 'xineliboutput --local=none --remote=37890'
        ExecStartPost=/usr/local/bin/svdrpsend.pl remo off
        Restart=on-failure
(Continue reading)

Permalink | Reply |
headers
Ludwig Nussel | 27 Jun 2012 13:16
Picon
Gravatar

Re: Please share your systemd (Upstart) service file

Paul Menzel wrote:
> [...]
> and the one shipped by openSUSE [2].
>
>          [Unit]
>          Descritpion=VDR
>          After=lirc.service
>
>          [Service]
>          Type=once
>          ExecStart=/usr/local/bin/runvdr
>          TimeoutSec=0

The reference to /usr/local makes it pretty obvious that this isn't part
of any distro.

> As the comments in the VDR-Portal thread [2] suggest, it would be great
> to do without any shell/Bash script and more or less execute plain VDR
> and let systemd do everything else.

Yes. Not only for better systemd integration but in general it would be
better if vdr could work without requiring any external scripting or
configuration.

cu
Ludwig

--

-- 
  (o_   Ludwig Nussel
  //\
(Continue reading)

Permalink | Reply |
headers
Manuel Reimer | 27 Jun 2012 18:32
Picon
Picon

Re: Please share your systemd (Upstart) service file

Ludwig Nussel wrote:
> Yes. Not only for better systemd integration but in general it would be
> better if vdr could work without requiring any external scripting or
> configuration.

You need some external script to call VDR as somewhere it is required to 
configure plugins and plugin parameters and many more stuff, VDR gets via 
command line options.

Every distribution handles this thing a bit different. For example, I prefer to 
use "runvdr-extreme" and configure my stuff in the "runvdr.conf" file.

BTW: "systemd" is one of many init systems. I don't know why this system is that 
special, that it deserves upstream integration. Especially as this would just 
reflect the defaults of *one* distribution. Another distribution most probably 
has other ways to configure plugins and settings.

Yours

Manuel

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Permalink | Reply |
headers
Darren Salt | 27 Jun 2012 18:51
Picon

Re: Please share your systemd (Upstart) service file

I demand that Manuel Reimer may or may not have written...

[snip]
> BTW: "systemd" is one of many init systems. I don't know why this system is
> that special, that it deserves upstream integration. Especially as this
> would just reflect the defaults of *one* distribution.

And we all know which one.

> Another distribution most probably has other ways to configure plugins and
> settings.

So far as I'm concerned, systemd people wanting these files in systemd and
*not* where they really belong is just plain... lock-in.

Updating the file could be interesting, particularly if you need to update it
so that you can do a new release – suddenly you're tied to their release
schedule. What if releases are ‘carefully’ timed?

Assuming that that actually is the case, of course; if not, then fine, no
problem. I currently plan to stick with SysV and related tools regardless,
though.

--

-- 
|  _  | Darren Salt, using Debian GNU/Linux (and Android)
| ( ) |
|  X  | ASCII Ribbon campaign against HTML e-mail
| / \ | http://www.asciiribbon.org/

You can't antagonise and influence at the same time.
(Continue reading)

Permalink | Reply |
headers
Ludwig Nussel | 28 Jun 2012 09:01
Picon
Gravatar

Re: Please share your systemd (Upstart) service file

Manuel Reimer wrote:
> Ludwig Nussel wrote:
>> Yes. Not only for better systemd integration but in general it would be
>> better if vdr could work without requiring any external scripting or
>> configuration.
>
> You need some external script to call VDR as somewhere it is required
> to configure plugins and plugin parameters and many more stuff, VDR
> gets via command line options.

That's the current state. I can't think of a good reason why it has to
stay that way though. VDR itself could have a menu that allows to enable,
disable and configure plugins.

cu
Ludwig

--

-- 
  (o_   Ludwig Nussel
  //\
  V_/_  http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Permalink | Reply |
headers
VDR User | 28 Jun 2012 19:02
Picon

Re: Please share your systemd (Upstart) service file

On Thu, Jun 28, 2012 at 12:01 AM, Ludwig Nussel <ludwig.nussel <at> suse.de> wrote:
>> You need some external script to call VDR as somewhere it is required
>> to configure plugins and plugin parameters and many more stuff, VDR
>> gets via command line options.
>
> That's the current state. I can't think of a good reason why it has to
> stay that way though. VDR itself could have a menu that allows to enable,
> disable and configure plugins.

That would be a nice feature -- worth suggesting for the big `after
2.0 is released` redesign(?). But, there may be plugins which need to
be initialized with certain values. Although, maybe it's possible to
have those be reinitialized within vdr?

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Permalink | Reply |
headers
Mika Laitio | 28 Jun 2012 20:07
Favicon

Re: Please share your systemd (Upstart) service file

On 06/28/2012 08:02 PM, VDR User wrote:
> On Thu, Jun 28, 2012 at 12:01 AM, Ludwig Nussel <ludwig.nussel <at> suse.de> wrote:
> That would be a nice feature -- worth suggesting for the big `after
> 2.0 is released` redesign(?). But, there may be plugins which need to
> be initialized with certain values. Although, maybe it's possible to
> have those be reinitialized within vdr?

Yeah, I would like to have option to pass path to plugin config file
for vdr-executable. Then somebody could write simple ui app for
configuting it via ui based on to plugins it finds from the PLUGINS dir.

In the case of systemd, it's no need to have this vdr has died, unload
and load kernel module loop in the runvdr script, as those can be
specified also as a pre and post commands in systemd.

Mika

> 
> _______________________________________________
> vdr mailing list
> vdr <at> linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Permalink | Reply |
headers
Gerald Dachs | 29 Jun 2012 12:59
Picon

Re: Please share your systemd (Upstart) service file

Am 28.06.2012 09:01, schrieb Ludwig Nussel:
> Manuel Reimer wrote:
>> Ludwig Nussel wrote:
>>> Yes. Not only for better systemd integration but in general it would be
>>> better if vdr could work without requiring any external scripting or
>>> configuration.
>>
>> You need some external script to call VDR as somewhere it is required
>> to configure plugins and plugin parameters and many more stuff, VDR
>> gets via command line options.
>
> That's the current state. I can't think of a good reason why it has to
> stay that way though. VDR itself could have a menu that allows to enable,
> disable and configure plugins.

I can't see a benefit of this approach. At least for distributors it 
would get more complicated to install plugins with a specific default 
configuration, because that would mean all configuration informations 
would go into the setup.conf and it is no good idea to manipulate this 
file from outside.

I would like to see the first user of this idea to try to disable a 
plugin that prevents the start of the vdr because of binary 
incompatibility. Must be funny.

Gerald

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
(Continue reading)

Permalink | Reply |
headers
Manuel Reimer | 2 Jul 2012 18:39
Picon
Picon

Re: Please share your systemd (Upstart) service file

Gerald Dachs wrote:
>> That's the current state. I can't think of a good reason why it has to
>> stay that way though. VDR itself could have a menu that allows to enable,
>> disable and configure plugins.
>
> I can't see a benefit of this approach. At least for distributors it would get
> more complicated to install plugins with a specific default configuration,
> because that would mean all configuration informations would go into the
> setup.conf and it is no good idea to manipulate this file from outside.

Exactly!

Again: systemd ist *one of many* init solutions and I guess, that Klaus doesn't 
use a distribution with systemd.

IMHO the "systemd people" will have to create some kind of "adapter script" (and 
maybe just call it "runvdr" ;) ).

"runvdr-extreme" comes with a solution to enable/disable plugins from the VDR 
GUI. Maybe that would fit as a base for systemd startup.

Yours

Manuel

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
(Continue reading)

Permalink | Reply |
headers
Klaus Schmidinger | 2 Jul 2012 23:51
Picon
Favicon

Re: Please share your systemd (Upstart) service file

On 02.07.2012, at 10:39, Manuel Reimer <manuel.reimer <at> gmx.de> wrote:

> Gerald Dachs wrote:
>>> That's the current state. I can't think of a good reason why it has to
>>> stay that way though. VDR itself could have a menu that allows to enable,
>>> disable and configure plugins.
>> 
>> I can't see a benefit of this approach. At least for distributors it would get
>> more complicated to install plugins with a specific default configuration,
>> because that would mean all configuration informations would go into the
>> setup.conf and it is no good idea to manipulate this file from outside.
> 
> Exactly!
> 
> Again: systemd ist *one of many* init solutions and I guess, that Klaus doesn't use a distribution with systemd.

No, I don't.

VDR (and me, too ;-) doesn't care in what way a particular system boots
or starts its services.
The 'runvdr' script that comes with the VDR source is merely a suggestion
of how to create an environment in which VDR can be (re-)started.

Klaus

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
(Continue reading)

Permalink | Reply |
headers
Torgeir Veimo | 3 Jul 2012 01:19

Re: Please share your systemd (Upstart) service file

On 3 July 2012 07:51, Klaus Schmidinger <Klaus.Schmidinger <at> tvdr.de> wrote:

> VDR (and me, too ;-) doesn't care in what way a particular system boots
> or starts its services.

It would be handy though, if VDR proper came default with a way to
toggle plugins on and off in the user interface.

--

-- 
-Tor

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Permalink | Reply |
headers
Udo Richter | 3 Jul 2012 21:33
Picon
Picon

Re: Please share your systemd (Upstart) service file

> On 3 July 2012 07:51, Klaus Schmidinger <Klaus.Schmidinger <at> tvdr.de> wrote:
> 
> > VDR (and me, too ;-) doesn't care in what way a particular system boots
> > or starts its services.
> 
> It would be handy though, if VDR proper came default with a way to
> toggle plugins on and off in the user interface.

It is nice, but as an additional option. But you absolutely need a way to enable/disable/configure plugins
from the outside of VDR, in case that a plugin crashes on startup, an output plugin does not output in
default configuration, remote is not working, or similar.

runvdr-extreme for example can enable/disable plugins via menu, but you can also do it via a command line
tool, or by setting/deleting rc?.d-like symbolic links.

Cheers,

Udo

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Permalink | Reply |
headers
Ville Skyttä | 27 Jun 2012 16:45
Picon
Picon
Favicon

Re: Please share your systemd (Upstart) service file

On 2012-06-27 12:48, Paul Menzel wrote:

> looking around for systemd service files I found three examples.

The Fedora one and other related files are at
http://pkgs.fedoraproject.org/gitweb/?p=vdr.git;a=tree

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Permalink | Reply |
headers
Steve Ross | 29 Jun 2012 17:21

Re: Please share your systemd (Upstart) service file


Mika Laitio <lamikr <at> pilppa.org> wrote:

>On 06/28/2012 08:02 PM, VDR User wrote:
>> On Thu, Jun 28, 2012 at 12:01 AM, Ludwig Nussel <ludwig.nussel <at> suse.de> wrote:
>> That would be a nice feature -- worth suggesting for the big `after
>> 2.0 is released` redesign(?). But, there may be plugins which need to
>> be initialized with certain values. Although, maybe it's possible to
>> have those be reinitialized within vdr?
>
>Yeah, I would like to have option to pass path to plugin config file
>for vdr-executable. Then somebody could write simple ui app for
>configuting it via ui based on to plugins it finds from the PLUGINS dir.
>
>In the case of systemd, it's no need to have this vdr has died, unload
>and load kernel module loop in the runvdr script, as those can be
>specified also as a pre and post commands in systemd.
>
>Mika
>
>
>> 
>> _______________________________________________
>> vdr mailing list
>> vdr <at> linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>
>
>_______________________________________________
>vdr mailing list
(Continue reading)

Permalink | Reply |

Gmane