config-linux: Many config properties without RFC 2119 language #746
Description
I've filed #745 to add RFC 2119 language to disableOOMKiller, but there are many other settings in config-linux.md without RFC 2119 wording to connect them with compliance testing (e.g. oomScoreAdj, memory, …). Without RFC 2119 language, it is not very clear what config-author and runtime responsibilities are intended to be. And it is clear that, whatever the intentions were:
- A config would be technically valid with ridiculous values in the setting (e.g.
"oomScoreAdj" = 999999999999999999999999999999999999999999999999999999999999999999). - A runtime would be technically valid if it silently ignored the setting.
I think we should address this before cutting 1.0. #745 is a (small) step in that direction, but I wanted to open this issue to get feedback on the issue in general (without getting bogged down on a specific setting).