Where Does tuned Store Config?
tuned keeps daemon config in /etc/tuned on Linux with distro profiles under lib. Old layouts vary by release.
Last updated
tuned splits daemon config from profiles across etc and lib trees. Custom profiles override distro defaults on collisions with version-dependent nesting. State persists under var with sockets beside.
Old layouts flatten what new releases nest, so match docs to distro age. Copy lib trees into etc for customization. Admin tools query live state beyond files.
Where tuned stores this, by platform
/etc/tuned/tuned-main.conf
Daemon config with custom profiles overriding lib defaults. Old layouts nest flatter per release. State persists under var with sockets.
Frequently asked questions
How do I back up tuned?
Copy /etc/tuned with custom profiles plus active markers while the daemon is stopped. Distro trees hold defaults to copy from, never edit. Old layouts nest flatter on retired releases.
Custom versus distro tuned profiles?
They pair per role with custom trees overriding lib defaults on collisions. Version splits nest profile folders differently across releases. Copy lib to etc for custom variants.
Where is tuned state?
It persists under var lib with run sockets and logs beside. Constants files name every path in source. Query through admin tools rather than raw files.
Notice an outdated path? Let us know.