Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Lock filesystem #156

Closed
varrel1337 opened this issue Oct 6, 2019 · 2 comments
Closed

Lock filesystem #156

varrel1337 opened this issue Oct 6, 2019 · 2 comments
Labels
question

Comments

@varrel1337
Copy link

Running 'fscrypt unlock DIRECTORY' will make the files in that directory available.
However, how do I "lock" that directory again? Currently the only way to do this seems to be a reboot of the system.
@ebiggers
Copy link
Collaborator

ebiggers commented Oct 6, 2019

You can use fscrypt purge, but it operates on a whole filesystem rather than an individual directory, it requires root, and it won't tell you whether any files couldn't be locked due to still being open. #148 will add an fscrypt lock command that works properly.

@varrel1337
Copy link
Author

Nice, thanks for the info

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ebiggers @varrel1337