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.

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

Fix wrong doc on exit code #503

Closed
wants to merge 1 commit into from
Closed

Fix wrong doc on exit code #503

wants to merge 1 commit into from

Conversation

yajo
Copy link

@yajo yajo commented Sep 5, 2020

According to real world tests, the correct exit code here is 7, so I'm updating the man page to avoid confusion.

See this session:

[root@132973203c5d /]# gocryptfs -init root
Invalid cipherdir: directory /root not empty
[root@132973203c5d /]# echo $?
7
[root@132973203c5d /]# gocryptfs --version
gocryptfs v1.8.0-Fedora-1.8.0-1.fc32; go-fuse 1.0.1; 2020-05-21 go1.14.2 linux/amd64

According to real world tests, the correct exit code here is 7, so I'm updating the man page to avoid confusion.

See this session:

```bash
[root@132973203c5d /]# gocryptfs -init root
Invalid cipherdir: directory /root not empty
[root@132973203c5d /]# echo $?
7
[root@132973203c5d /]# gocryptfs --version
gocryptfs v1.8.0-Fedora-1.8.0-1.fc32; go-fuse 1.0.1; 2020-05-21 go1.14.2 linux/amd64
```
rfjakob added a commit that referenced this pull request Sep 6, 2020
@rfjakob
Copy link
Owner

rfjakob commented Sep 6, 2020

Hi, thanks for the report! I looked at this, and I think gocryptfs returns the wrong exit code. So I fixed that and kept the docs as-is: 993b19c .

@rfjakob rfjakob closed this Sep 6, 2020
@rfjakob
Copy link
Owner

rfjakob commented Sep 6, 2020

PS: The fix will appear in gocryptfs v2.0, which currently being developed in the gofuse_v2api branch

@yajo yajo deleted the patch-1 branch September 7, 2020 10:30
mpobaschnig added a commit to mpobaschnig/vaults that referenced this pull request Nov 1, 2021
With gocryptfs v2.0, error codes were fixed, see: rfjakob/gocryptfs#503
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants