https://bugzilla.redhat.com/show_bug.cgi?id=839527
--- Comment #4 from Fernando Lopez-Lezcano nando@ccrma.stanford.edu --- (In reply to comment #3)
(In reply to comment #2)
- I really don't like the idea to introduce another SysVinit-script. It
won't be easy to switch to systemd later.
Why is that?
You may use the following approach
which is used in libvirt-clients
I thought long and hard about this whilst I was preparing this for review but am hesitant to do this - I'm sure Rui upstream will get there eventually and I'd prefer to leave it up to him (he's started packaging for Suse so I'm sure he'll get there). As this is moving from CCRMA I'm also very cognizant of shifting the ground under the feet of current users.
Copied Fernando for comment
I would not mind moving to systemd but Rui should be in the loop, I think. I considered it when rebuilding for fc17 but I had no time at all to learn systemd.
==============
[Unit] Description=Realtime IRQ thread tunning After=sound.target alsa-restore.service
Why would alsa-restore.service be a dependency? (if that is the term). Rtirq should happen after all kernel sound drivers are loaded and that's all it needs, I think.
[Service] EnvironmentFile=-/etc/sysconfig/rtirq ExecStart=/usr/bin/rtirq.sh start ExecStop=/usr/bin/rtirq.sh stop
There is also a status target that lists the current irq ordering.
[Install] WantedBy=multi-user.target
==============