commit 88c3d4896af6c09de5d360d93ad8b02793aeb234
from: Alexander Barton <alex@barton.de>
date: Wed Mar 28 09:30:48 2012 UTC

Don't ignore "permission denied" errors when enabling chroot

Up to now, ngIRCd silently ignored permission denied errors when trying
to enable a chroot setup: only the "not running chrooted" message became
logged later on.

This patch lets ngIRCd exit with a fatal error when the chroot can't
be enabled on startup -- this is the much safer bevahiour!

commit - 7b6ef3bc8eef8a084bc77155e4cd64a35198aad9
commit + 88c3d4896af6c09de5d360d93ad8b02793aeb234
blob - 60d15a1f8a7be1afe807d192f52223e4dffac50a
blob + f28ff05bcfb778065dc99a50e7459472eee8a68f
--- src/ngircd/ngircd.c
+++ src/ngircd/ngircd.c
@@ -642,12 +642,10 @@ NGIRCd_Init(bool NGIRCd_NoDaemon)
 		}
 
 		if (chroot(Conf_Chroot) != 0) {
-			if (errno != EPERM) {
-				Log(LOG_ERR,
-				    "Can't change root directory to \"%s\": %s",
-				    Conf_Chroot, strerror(errno));
-				goto out;
-			}
+			Log(LOG_ERR,
+			    "Can't change root directory to \"%s\": %s",
+			    Conf_Chroot, strerror(errno));
+			goto out;
 		} else {
 			chrooted = true;
 			Log(LOG_INFO,