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

Need workaround for libfuse ticket #15 #33

Closed
rfjakob opened this issue Aug 12, 2016 · 1 comment
Closed

Need workaround for libfuse ticket #15 #33

rfjakob opened this issue Aug 12, 2016 · 1 comment

Comments

@rfjakob
Copy link
Owner

rfjakob commented Aug 12, 2016

libfuse/libfuse#15
@rfjakob rfjakob changed the title Need workaround for libfuse bug #15 Need workaround for libfuse ticket #15 Aug 16, 2016
@rfjakob
Copy link
Owner Author

rfjakob commented Aug 17, 2016

Actually, we don't. default_permissions work fine. IMO, libfuse/libfuse#15 is NOTABUG.

@rfjakob rfjakob closed this as completed Aug 17, 2016
@pos42 pos42 mentioned this issue Oct 12, 2018
Closed
rfjakob added a commit that referenced this issue Oct 17, 2018
@rfjakob
tlog: disable color codes when switching to syslog
1ed08c7 
When gocryptfs was started on a terminal and later
daemonized, the color codes stayed active in the syslog
output.

The codes are not visible in "journalctl -f", which is why
I have not noticed it yet, but they do show up in normal
syslog as the usual "#33[33m" crap.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rfjakob