{{ message }}
check_disk: Add synthetic file systems for default exclusion depending on command line options.#1749
Open
mirespace wants to merge 1 commit into
Conversation
EnanTompil
approved these changes
Jan 31, 2022
Member
they have not been included and no mount point have been provided
in command line. Fixes monitoring-plugins#1748 .
10a5a92 to
d062d28
Compare
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Hi,
to avoid false-positive DISK CRITICAL error and DISK UNKNOWN message when using check_disk with tracefs, squasfs and tmpfs (synthetic filesystems), the approach here has been to exclude this type of filesystem only if it is neither included via path (option -p) nor via include (option -N). I think it can help in cases that scripts are in place and flags cannot be wrapped.
Fixes #1748.