-
Notifications
You must be signed in to change notification settings - Fork 38
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
[feature request]: progress indicator #31
Comments
It does print out which files it is changing permissions for when it encounters a file that needs permissions changed, so long as you don't use the It is slow if you are walking large container filesystems. If that's the case, a better thing to do would be to point That can be accomplished through using the https://github.com/boxboat/fixuid#specify-paths-and-behavior-across-devices |
Thank you. I was using the q flag so that explains it. I am already using the paths array too. Thanks!
…-------- Original Message --------
On Oct 14, 2020, 16:29, Caleb Lloyd wrote:
It does print out which files it is changing permissions for when it encounters a file that needs permissions changed, so long as you don't use the -q flag to silence the output
It is slow if you are walking large container filesystems. If that's the case, a better thing to do would be to point fixuid to only scan the paths where it may encounter files that need UIDs changed
That can be accomplished through using the paths: array in the config:
https://github.com/boxboat/fixuid#specify-paths-and-behavior-across-devices
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#31 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAHH5PINWDBOGGCVDINGHT3SKYJ2FANCNFSM4SRATY6A).
|
fixuid can sometimes be rather slow, leaving the user wondering what's wrong, often they will then try to cancel out of the command. Can we have some sort of indicator to let the user know that permissions are being changed in the container?
The text was updated successfully, but these errors were encountered: