-
Notifications
You must be signed in to change notification settings - Fork 4
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
Reduce chaperone
Load by Pruning Special FS Types from find Searches
#1
Comments
I'm not certain about the frequency of the operation - whether it's every 1 or 5 minutes - but I would suggest extending the interval to at least I would generally recommend using |
This was in some initial releases, go ahead and propose the change. |
is how it works, you use arguments to control Chaperone. |
The app watches pods, not data. |
"Watches the pods" implies scanning their data ("data" - in the context of the data paths, i.e. the directories, filenames; obviously not the contents). |
The
chaperone
utility employs the commandfind / -type f ...
to search through pods.This search inadvertently includes non-filesystem-based paths such as
/proc
,/sys
, etc.Such inclusion not only generates additional processing load but can also lead to issues. I recall instances from a few years ago when the
find /
command would get indefinitely stuck.I recommend using the command
find / \( -fstype proc -o -fstype sysfs -o -fstype tmpfs \) -prune -o -type f
to specifically exclude special filesystem types likeproc
,sysfs
, andtmpfs
.In this instance, a single
find
command unnecessarily scans an additional62,201
files.@88plug
The text was updated successfully, but these errors were encountered: