WIP: Closes #11 Added IS_HOME_SIZE #58
No reviewers
Labels
No Label
bug
bullseye
discussion
duplicate
enhancement
help wanted
invalid
question
suggestion
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Blocks
#11 Check for sysadmins home size
evolix/evocheck
Reference: evolix/evocheck#58
Loading…
Reference in New Issue
No description provided.
Delete Branch "11-Check-for-sysadmins-home-size"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We loop for all sysadmins home dir (using evomaintenance trap) and calculate
their home size. By default warn if more than 1G.
Is not overkill to run du command for every admin accounts ?
That risk to be very long if an account have a big home.
Add a timeout or exit on some size ?
I thought about that, but the case where an admin have many small files (take more time than big file to compute) or a very large home must be really rare so I havn't specified any timeout or any fuse break method...
I wonder what could be the best method?
timeout
need to be installed on the system, it may be unavailable.Any ideas?
Closes #11 Added IS_HOME_SIZEto WIP: Closes #11 Added IS_HOME_SIZEThis issue/PR is temporarily suspended, now in WIP mode.
Could with run it with something like SIGALRM?
https://en.wikipedia.org/wiki/Signal_(IPC)#SIGALRM
We should not call perl. Also this check may be never added to production.
It may be enabled when evocheck will have a debug-like mode which do plenty of other "heavy" checks or something like that.
For now this idea is suspended.
The same thing can be done with a very small c program, but I get your point.
Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Forgejo.