aboutsummaryrefslogtreecommitdiff
path: root/internal/exitcodes/exitcodes.go
diff options
context:
space:
mode:
authorJakob Unterwurzacher2017-05-23 18:01:21 +0200
committerJakob Unterwurzacher2017-05-23 18:01:21 +0200
commit508fd9e1d64131958c86175cb8d848f730e629cf (patch)
tree6d6d9370bf9760af229e93bbea29cb0f9cf4f494 /internal/exitcodes/exitcodes.go
parent245b84c887955d12cd1113e9a6701ee7338c8255 (diff)
main: downgrade panic log create failure from fatal error to warning
Exiting with a fatal error just pushes users to use "-nosyslog", which is even worse than not having a paniclog.
Diffstat (limited to 'internal/exitcodes/exitcodes.go')
-rw-r--r--internal/exitcodes/exitcodes.go5
1 files changed, 3 insertions, 2 deletions
diff --git a/internal/exitcodes/exitcodes.go b/internal/exitcodes/exitcodes.go
index ae7824d..88e8e5f 100644
--- a/internal/exitcodes/exitcodes.go
+++ b/internal/exitcodes/exitcodes.go
@@ -49,8 +49,9 @@ const (
FuseNewServer = 19
// CtlSock - the control socket file could not be created.
CtlSock = 20
- // PanicLogCreate - there was a problem creating the /tmp/gocryptfs_paniclog.XYZ file.
- PanicLogCreate = 21
+ // Downgraded to a warning in gocryptfs v1.4
+ //PanicLogCreate = 21
+
// PasswordEmpty - we received an empty password
PasswordEmpty = 22
// OpenConf - the was an error opening the gocryptfs.conf file for reading