This one is a bit weird. procps itself ships /etc/init.d/procps, and
does not have a systemd unit. But, the systemd package creates a
symlinks /usr/lib/systemd/system/procps.service ->
/usr/lib/systemd/system/systemd-sysctl.service, which has always made
the sysv-generator ignore /etc/init.d/procps.
$ SYSTEMD_LOG_LEVEL=debug
/usr/lib/systemd/system-generators/systemd-sysv-generator /tmp/fakeroot |& grep
procps
Native unit for procps.service already exists, skipping.
Overall this makes sense: systemd-sysctl is used (instead if
/usr/sbin/sysctl) to load sysctl.d configs on systems where systemd is
installed. But the current implementation of this in the packaging is a
little obscure.
** Changed in: procps (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2153900
Title:
procps: System V script needs to be migrated to systemd service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2153900/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
