All, What are the rules for 13.1 concerning what should be enabled through systemctl and what should be launched via init-script and set through chkconfig? I understand 13.1 uses sysv compatibility and retains consolekit, and init-scripts, but that is a bit confusing considering there may be service files and init-scripts for some packages. My prior systemd experience has been with my Archlinux installs. Arch moved to a pure-systemd setup over a year ago. 13.1 is my first install that implements systemd in somewhat of a compatibility mode. For example: OpenSuSE 13.1: $ l /etc/init.d total 456 drwxr-xr-x 2 root root 4096 Jul 12 20:49 boot.d drwxr-xr-x 2 root root 4096 Sep 27 2013 rc0.d drwxr-xr-x 2 root root 4096 Sep 27 2013 rc1.d drwxr-xr-x 2 root root 4096 Jul 14 20:28 rc2.d drwxr-xr-x 2 root root 4096 Jul 14 20:28 rc3.d drwxr-xr-x 2 root root 4096 Sep 27 2013 rc4.d drwxr-xr-x 2 root root 4096 Jul 14 20:28 rc5.d drwxr-xr-x 2 root root 4096 Sep 27 2013 rc6.d drwxr-xr-x 2 root root 4096 Sep 27 2013 rcS.d -rwxr--r-- 1 root root 3649 Feb 14 05:17 acpid -rwxr--r-- 1 root root 520 Jul 12 20:03 after.local -rwxr-xr-x 1 root root 5155 Nov 28 2013 alsasound -rwxr-xr-x 1 root root 3885 Mar 11 05:20 autofs -rwxr-xr-x 1 root root 1217 Feb 28 06:22 avahi-daemon <snip> Archlinux: $ l /etc/init.d ls: cannot access /etc/init.d: No such file or directory In arch all services were required to be started via systemctl and all init-scripts were migrated (or upstream provided) service files. Now I find myself wondering: "What's the rule for 13.1?" When I configure mariaDB, do I use the service file or the init-script? What about for spamd, or hddtemp? Is there any penalty in overhead if I choose one way over the other? What say the systemd gurus? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org