clone 756375 -1 reassign -1 ulatency retitle -1 ulatencyd conflicts with default systemd configuration found -1 0.5.0-9 thanks
Am 07.08.2014 11:07, schrieb Michael Biebl:
> Am 07.08.2014 11:00, schrieb johnw:
>> After upgrade systemd-* to 208-7, I still have this problem.
>> Please help, thank you.
>
> Have you tried uninstalling/purging the ulatencyd package?
>
Or tried the instructions at [1]
4 Does it work with systemd
Since Version 0.4.5 ulatencyd works with systemd under two conditions:
DefaultControllers should be unset. In
/etc/systemd/system.conf set DefaultControllers=
JoinControllers should be unset. In /etc/systemd/system.conf
set JoinControllers=
The PAM-systemd module should be disabled, or set "controllers="
Both options would cause constant moving of processes as the layout
of systemd and ulatencyd (in the default configuration) differs.
Disabling the pam module will break a lot of functionality modern
desktops require, so we can certainly not ship that in Debian as default
configuration for systemd.
I guess there is not a lot we can do about this in the systemd package.
We could add a Conflicts: ulatencyd to make sure the package is not
installed. But given that systemd will be the default init system for
Jessie, this will make the ulatencyd package mostly useless.
Maybe the ulatencyd package should ship the service as disabled by
default. With clear instructions how to enable it under systemd and what
consequences that has.
In any case, bringing the ulatencyd package maintainer into the loop
here and clonging the bug.
Michael
[1] https://github.com/poelzi/ulatencyd/wiki/Faq#does-it-work-with-systemd
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
