From 508fd9e1d64131958c86175cb8d848f730e629cf Mon Sep 17 00:00:00 2001
From: Jakob Unterwurzacher
Date: Tue, 23 May 2017 18:01:21 +0200
Subject: 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.
---
 internal/exitcodes/exitcodes.go | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'internal/exitcodes/exitcodes.go')

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
-- 
cgit v1.2.3