On 19 Dec 2024, at 11:16, Livius via lists.openembedded.org
<egyszeregy=freemail...@lists.openembedded.org> wrote:
> +# To make use of the hardware watchdog it is sufficient to set
> WATCHDOG_RUNTIME_SEC
> +# (RuntimeWatchdogSec= option in /etc/systemd/system.conf) to a value like
> 20s
> +# and the watchdog is enabled. (defaults is no hardware watchdog use)
> +WATCHDOG_RUNTIME_SEC ??= ""
> +
> + if [ -n "${WATCHDOG_RUNTIME_SEC}" ]; then
> + sed -i -e
> 's/#RuntimeWatchdogSec=off/RuntimeWatchdogSec=${WATCHDOG_RUNTIME_SEC}/' \
> + ${D}/${sysconfdir}/systemd/system.conf
> + fi
We’re slowly adding more variables for system.conf, which is explictly designed
to be extended with configuration snippets. The logical conclusion of this is
that every option in system.conf has a variable in the recipe to set it.
A more scalable approach would be to just use configuration snippets, ie you
write your watchdog assignments to /etc/systemd/system.conf.d/watchdog.conf.
This doesn’t involve touching the systemd recipe and will override the defaults.
What do you think about this approach?
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#209564):
https://lists.openembedded.org/g/openembedded-core/message/209564
Mute This Topic: https://lists.openembedded.org/mt/110196053/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
