-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Folders plugin always fails on special directories #2518
Comments
Hi @Ellpeck Please run Glances in debug mode (-d) and search for the "Cannot get folder size" pattern in the Glances log file and copy paste the result. On my side, with the following configuration:
I have:
|
With my configuration (which, again, I'd like to use to display the size of the docker volumes and related files)
I get pretty much the same message:
|
Done in the develop branch (will be release in Glances 4.0.0). The new behavor is the following: if a file (or subfolder) is not readable, it is ignored by Glances and a special char (?) / color is displayed in the console and Web UI. @Ellpeck Can you test it ? |
Hi! I tested the change as you requested. Unfortunately, using the
|
Patch merged into develop for the PermissionError. Will be release in Glances 4.0.0. Thanks for the report @Ellpeck (and sorry for the delay). |
Is your feature request related to a problem? Please describe.
Hi again!
In addition/relation to #2494, I found another issue: The folders plugin errors when it fails to detect the size of the
proc
directory on Linux, which causes an issue for displaying the size of directories like the docker volume directory, since those also contain versions ofproc
.Obviously, this makes sense and is in line with other tools, but those tools just display an error and continue scanning directory sizes instead of failing altogether. This is
ncdu
for example:Describe the solution you'd like
Potentially, it would also make sense for the folders plugin to either display an error and continue scanning rather than failing outright, or to be able to specify a set of file names (maybe through a regular expression or a glob pattern?) that should be ignored when scanning, or to ignore
proc
specifically since it's a special directory.Additional context
As I said at the top, this issue is somewhat in relation to #2494, which was fixed incredibly quickly & effectively, so thanks so much again for that!!
The text was updated successfully, but these errors were encountered: