This continues to cause breakage - https://bugs.launchpad.net/charm- sysconfig/+bug/1873028
I'm still looking for a modern justification for it to exist - considering AFAIK no other distro does this. ** Description changed: Ondemand init script is not inherited from Debian, it's an Ubuntu specific change. Some reasons to get rid of it: On my wily cloud test, systemd blame's 669ms on ondemand on a cloud instance with no ability to change frequency.. - In the init script we don't run this for android - Ondemand is already on by default! Why don't we just always use whatever is that kernel's default? + In the init script we don't run this for android + Why don't we just always use whatever is that kernel's default? There are a number of other reported problems with it: https://launchpad.net/ubuntu/+source/sysvinit/+bugs?field.searchtext=ondemand -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1503773 Title: Drop ondemand init script Status in systemd package in Ubuntu: New Status in sysvinit package in Ubuntu: Fix Released Bug description: Ondemand init script is not inherited from Debian, it's an Ubuntu specific change. Some reasons to get rid of it: On my wily cloud test, systemd blame's 669ms on ondemand on a cloud instance with no ability to change frequency.. In the init script we don't run this for android Why don't we just always use whatever is that kernel's default? There are a number of other reported problems with it: https://launchpad.net/ubuntu/+source/sysvinit/+bugs?field.searchtext=ondemand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1503773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
