cryptomator / cryptomator/cli

Ignored -onoatime

Open
#95 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
427
Forks
52
Avg merge
20h 37m
Merged PRs (30d)
2

Description

### Please agree to the following

- [x] I have searched [existing issues](https://github.com/cryptomator/cli/issues?q=) for duplicates
- [x] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/cli/blob/develop/.github/CODE_OF_CONDUCT.md)

### Summary

noatime fuse mount option is ignored

### What software is involved?

- Operating System: 6.12.57+deb13-amd64
- Cryptomator: cryptomator-cli 0.6.2
- fuse3 3.17.2-3

### Volume Type

FUSE

### Steps to Reproduce

1. CLI: cryptomator-cli unlock \
--password:stdin \
--mounter=org.cryptomator.frontend.fuse.mount.LinuxFuseMountProvider \
--mountPoint=/mnt/unlocked \
--mountOption=-ouid=1001 \
--mountOption=-ogid=1001 \
--mountOption=-oumask=077 \
--mountOption=-onoatime \
--mountOption=-oallow_other \
/mnt/vault
2. stat a file in the vault
3. shasum the file
4. stat the file again
5. Notice the access time got updated
6. findmnt confirms noatime option is active

### Expected Behavior

Access time is not updated and underlying files are unchanged.

### Actual Behavior

Access time is updated and underlying files are changed.

### Reproducibility

Always

### Relevant Log Output

```shell

```

### Anything else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.