Mariell Hoversholm c3fc9e0d0f fix(restart_handler): disable if there is no work ...

When there is no work to do, i.e. when all config watching is disabled,
there is no need to keep the restart_handler running. Disable it in this
case.

This is helpful to do on nodes where there is little to no headroom in
terms of open inotify watches (as per the inotify/max_user_instances
configuration), as can happen on nodes populated with other software
that also watch the filesystem for changes. If Falco is run on such a
node, it may fail to start due to functionality the app does not even
intend on using.

This has one change in terms of behaviour, however: the dry-run restarts
will no longer occur. As there is still never going to happen a real
restart, I understand it as unlikely for there to be a proper need for
dry-run restarts.

Signed-off-by: Mariell Hoversholm <mariell@grafana.com>

2025-07-24 12:56:39 +02:00

..

engine

update(userspace/engine): update falco engine version and checksum

2025-07-22 14:30:29 +02:00

falco

fix(restart_handler): disable if there is no work

2025-07-24 12:56:39 +02:00