Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

memory-monitor: Fix memory monitor config update for debug container. #4453

Conversation

OhmSpectator
Copy link
Member

@OhmSpectator OhmSpectator commented Dec 2, 2024

Update the pkill command in the memory-monitor-update-config case to use the process name (memory-monitor) instead of the full path (/sbin/memory-monitor). This change ensures compatibility with the debug container, which uses procps-ng version 3.3.17 that does not support full paths in the pkill command.

This adjustment makes the command functional when executed in the debug container, improving usability for users connecting via SSH.

To be backported into 13.4.0-stable

Update the pkill command in the memory-monitor-update-config case to use
the process name (memory-monitor) instead of the full path
(/sbin/memory-monitor). This change ensures compatibility with the debug
container, which uses procps-ng version 3.3.17 that does not support
full paths in the pkill command.

This adjustment makes the command functional when executed in the debug
container, improving usability for users connecting via SSH.

Signed-off-by: Nikolay Martyanov <[email protected]>
@OhmSpectator OhmSpectator requested review from deitch and rene December 2, 2024 17:14
@OhmSpectator OhmSpectator added bug Something isn't working stable Should be backported to stable release(s) labels Dec 2, 2024
@OhmSpectator OhmSpectator merged commit 3fc25e7 into lf-edge:master Dec 3, 2024
52 of 58 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stable Should be backported to stable release(s)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants