Hi, below is how rtirq currently looks like for the systemd based Wily and below that how a systemd solution could look like [1]. It shows the rtirq service file. Btw. moving rtirq to bin comes with a convenient side effect, a user simply can run "rtirq status" by command line, without a path or service wrapper.
Is there a reason that rtirq for Ubuntu Studio still is an init file for sysvinit or upstart usage and the used init process is ignored? What's the idea behind using systemd for the init process, but using wrappers to start init files instead of systemd unites? Regards, Ralf [1] [weremouse@moonstudio ~]$ apt-file list rtirq-init rtirq-init: /etc/default/rtirq rtirq-init: /etc/init.d/rtirq rtirq-init: /usr/share/doc/rtirq-init/changelog.Debian.gz rtirq-init: /usr/share/doc/rtirq-init/copyright [weremouse@moonstudio ~]$ sudo systemd-nspawn -D /mnt/archlinux/ [sudo] password for weremouse: Spawning container archlinux on /mnt/archlinux. Press ^] three times within 1s to kill container. Failed to create directory /mnt/archlinux/sys/fs/selinux: Read-only file system Failed to create directory /mnt/archlinux/sys/fs/selinux: Read-only file system [root@archlinux ~]# pacman -Ql rtirq rtirq /etc/ rtirq /etc/conf.d/ rtirq /etc/conf.d/rtirq rtirq /usr/ rtirq /usr/bin/ rtirq /usr/bin/rtirq rtirq /usr/lib/ rtirq /usr/lib/systemd/ rtirq /usr/lib/systemd/system/ rtirq /usr/lib/systemd/system/rtirq.service [root@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 [Install] WantedBy=multi-user.target -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
