tuned does not fail if the profile does not exist in daemon mode

[acottre]

We recently upgraded from 2.20 to 2.25 (via debian 12 -> 13) and did not realise initially that there was a breaking change in v2.23.0 that meant our custom profile was no longer in the correct path.

This went silent until someone noticed that the tunings had not been applied, and found the error in the log.

2026-04-22 10:51:54,763 ERROR    tuned.daemon.daemon: Cannot set initial profile. No tunings will be enabled: Requested profile 'non-existant-profile' doesn't exist.

Would it be acceptable for tuned to exit with a non-zero exit code if the profile does not exist? I would be happy if this was done via an additional config/command line flag

[yarda]

This wouls require another option that will have to be customized downstream, because the daemon needs to be running. It cannot exit by default with the error code, because it couldn't be controlled then (and the profile changed) via D-Bus, e.g. from the Cockpit frontend or tuned-ppd / desktop applet.