[ubuntu-studio-devel] Shouldn't rtirq become a systemd unit?

[Ralf Mardorf]

On Thu, 6 Aug 2015 09:06:10 -0700 (PDT), Len Ovens wrote:
>On Thu, 6 Aug 2015, Ralf Mardorf wrote:
>
>> below that how a systemd solution could look like [1].
>
>> [root at archlinux ~]# cat /usr/lib/systemd/system/rtirq.service
>> [Unit]
>> Description=Realtime IRQ thread system tuning
>> After=multi-user.target sound.target
>>
>> [Service]
>> Type=oneshot
>> ExecStart=/usr/bin/rtirq start
>> ExecStop=/usr/bin/rtirq stop
>> RemainAfterExit=true
>
>This is where sysinit/upstart/systemd kind of fail me. Stuff like this
>is really not a system service, but rather system configuration.
>
>In the above, what is there to stop? The script sets the system up and 
>exits. (I am guessing that is what oneshot means) So what is the
>remain after exit thing in this case? That doesn't make sense as there
>is (or should be) no remaining running process.

I'm a systemd user, but I don't like systemd and I much more dislike
the generator-hybrid-systemd.

What does Requires= After= Before= do, if you use it in several service
files? Everybody will lose track of the unit order.

http://www.freedesktop.org/software/systemd/man/systemd.unit.html

If you search by Ctrl+F you'll not find RemainAfterExit, oneshot.

I don't know where upstream documented everything.

That systemd already is hard to use is the reason why I dislike to mix
it with init files.