-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
Expose issues with file ownership / permissions / attributes (Ideally as part of "Scheduled Validation") #836
Comments
Hey Marc! This feature makes sense. However, it would imply that we won't be able to use I don't recall at the moment if we also apply We will need to wait for Jamie's comment on this. |
Checking permissions on all the files that Fix Permissions fixes could be really slow, so I don't think we could do this as part of scheduled validation. |
I understand.
Even just the number of files affected would be nice because it's a hint of the presence or absence of an issue. I have an idea: chown [-c|--changes] "displays information about files that are actually changed. For example: changed ownership of 'dir/dir1/file1' from hope:neil to hope:hope" |
We use Perl's
|
We could certainly show the list of files that were changed on the Fix Permissions page.. |
Yeah, I know. But I think we should make a new Virtualmin 7.20.0 release and keep this particular feature for later! We also need to wrap up Webmin and Usermin next week, as after that I need to finish the WordPress Workbench and start reworking Cloudmin. The time has come! |
Sure, let's keep as a nice-to-have one day. I look forward to 7.20.0! |
Can this ticket be closed? |
No yet. We are still missing:
|
Ah, that's right! |
It would be nice to know what it solved. It would be even nicer to have this as part of the scheduled validation. So we could quickly be alerted about issues (Usually, the sooner we know, the easier it is to address the root cause)
Many times, we have wasted time because someone worked as root and forgot to chown a file, or a script running as root created some files, some files were migrated from another site, and we forgot to change the owner, etc.
I realize it could be super slow to do this. So maybe it should be a check box in scheduled validation "Also validate file permissions".
The text was updated successfully, but these errors were encountered: