On Tue, Aug 18, 2015 at 6:36 AM, Ralf Mardorf <ralf.mard...@alice-dsl.net> wrote: > On Tue, 18 Aug 2015 05:40:23 -0400, Tom H wrote: >> >> It's a bit messy, SOMETIMES.
> I'm aware that it wasn't you who blamed me for spreading "unfounded > FUD", it was Oliver and at the same time he mentioned backwards > compatibility, inter-distro-compatibility, the feature that one command > does it all. I don't care about FUD or whatever. > AFAIK Ubuntu's systemd implementation doesn't provide any of those > three advantages, it brakes all three advantages [1]. > > The wrapper-workaround-approach leads to misinformation [1]. > > The mess could be avoided without much work, e.g. for > > http://packages.ubuntu.com/trusty/all/rtirq-init/filelist > > The Ubuntu maintainer just needs to correct the location and add a > service file, but even if you would provide the service file and > corrected file locations for the maintainer, you can't contribute to > Ubuntu. It's recommended to get in contact with Debian maintainers. > > [1] > For example: > > Imagine you'll maintain your install, using a workflow that can be used > for a clean systemd install. > > [weremouse@moonstudio ~]$ systemctl list-unit-files | grep alice > alice.service enabled > [weremouse@moonstudio ~]$ systemctl list-unit-files | grep rtirq > [weremouse@moonstudio ~]$ > > Looks like rtirq isn't enabled, but de facto it's enabled. > > [weremouse@moonstudio ~]$ systemctl list-units | grep alice > alice.service > loaded active exited Alice PPPoE > [weremouse@moonstudio ~]$ systemctl list-units | grep rtirq > rtirq.service > loaded active exited LSB: Realtime IRQ thread tunning. > [weremouse@moonstudio ~]$ systemctl status alice | grep active Active: > active (exited) since Mon 2015-08-17 22:55:32 CEST; 13h ago > [weremouse@moonstudio ~]$ systemctl status rtirq | grep active Active: > active (exited) since Mon 2015-08-17 22:55:33 CEST; 13h ago > > Regarding backwards compatibility, there is no backwards compatibility > when using the service wrapper. > Please correct me when I'm mistaken, didn't the service wrapper in the > past do the same as /etc/init.d/foo status does? > > [weremouse@moonstudio ~]$ service rtirq status > ● rtirq.service - LSB: Realtime IRQ thread tunning. > Loaded: loaded (/etc/init.d/rtirq) > Active: active (exited) since Mon 2015-08-17 22:55:33 CEST; 13h ago > Docs: man:systemd-sysv-generator(8) > > Warning: Journal has been rotated since unit was started. Log output is > incomplete or unavailable. > > [weremouse@moonstudio ~]$ /etc/init.d/rtirq status > > PID CLS RTPRIO NI PRI %CPU STAT COMMAND > 385 FF 90 - 130 0.0 S irq/18-snd_hdsp > 387 FF 85 - 125 0.0 S irq/20-snd_ice1 > 388 FF 84 - 124 0.0 S irq/21-snd_ice1 > 35 FF 50 - 90 0.0 S irq/9-acpi > 60 FF 50 - 90 0.0 S irq/19-ehci_hcd > 61 FF 50 - 90 0.0 S irq/16-ohci_hcd > 62 FF 50 - 90 0.0 S irq/17-ohci_hcd > 63 FF 50 - 90 0.0 S irq/18-ohci_hcd > 64 FF 50 - 90 0.0 S irq/17-ohci_hcd > 66 FF 50 - 90 0.0 S irq/18-ohci_hcd > 67 FF 50 - 90 0.0 S irq/1-i8042 > 68 FF 50 - 90 0.0 S irq/8-rtc0 > 135 FF 50 - 90 0.0 S irq/22-0000:00: > 145 FF 50 - 90 0.0 S irq/14-pata_ati > 149 FF 50 - 90 0.0 S irq/15-pata_ati > 157 FF 50 - 90 0.0 S irq/22-firewire > 164 FF 50 - 90 0.0 S irq/27-radeon > 275 FF 50 - 90 0.0 S irq/7-parport0 > 786 FF 50 - 90 0.0 S irq/26-enp3s0 > 3 TS - 0 19 0.0 S ksoftirqd/0 > 17 TS - 0 19 0.0 S ksoftirqd/1 Strange. This is on my laptop running 15.10. # systemctl --version systemd 224 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN # find /lib/systemd/system -name "*postfix*" # find /etc/init.d -name "*postfix*" /etc/init.d/postfix # find /run/systemd -name "*postfix*" /run/systemd/generator.late/postfix.service /run/systemd/generator.late/graphical.target.wants/postfix.service /run/systemd/generator.late/multi-user.target.wants/postfix.service /run/systemd/generator/mail-transport-agent.target.d/50-hard-dependency-postfix-$mail-transport-agent.conf /run/systemd/generator/postfix.service.d /run/systemd/generator/postfix.service.d/50-postfix-$mail-transport-agent.conf # systemctl | grep postfix postfix.service loaded active running LSB: Postfix Mail Transport Agent # systemctl status postfix.service ● postfix.service - LSB: Postfix Mail Transport Agent Loaded: loaded (/etc/init.d/postfix) Drop-In: /run/systemd/generator/postfix.service.d └─50-postfix-$mail-transport-agent.conf Active: active (running) since Sun 2015-08-16 03:56:28 EDT; 2 days ago <snip> # service postfix status ● postfix.service - LSB: Postfix Mail Transport Agent Loaded: loaded (/etc/init.d/postfix) Drop-In: /run/systemd/generator/postfix.service.d └─50-postfix-$mail-transport-agent.conf Active: active (running) since Sun 2015-08-16 03:56:28 EDT; 2 days ago <snip> # env -i LC_ALL=C PATH=/sbin:/bin:/usr/sbin:/usr/bin /etc/init.d/postfix status ● postfix.service - LSB: Postfix Mail Transport Agent Loaded: loaded (/etc/init.d/postfix) Drop-In: /run/systemd/generator/postfix.service.d └─50-postfix-$mail-transport-agent.conf Active: active (running) since Sun 2015-08-16 03:56:28 EDT; 2 days ago <snip> /usr/sbin/service is a shell script and it has: <begin> # When this machine is running systemd, standard service calls are turned into # systemctl calls. </end> And this is what you want for the sake of consistency. I don't understand how "/etc/init.d/postfix status" is diverted to systemctl for postfix but it is. Anyway, if you're booting with systemd as pid 1, why would you run "/etc/init.d/rtirq status"? -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
