commit 8d414b079c1b4b0b8c88c8ab5cf4b27bf0942752
from: Alexander Barton <alex@barton.de>
date: Sun May 03 15:08:51 2020 UTC

Correctly use Config_Error() instead of Log() in Read_Config()

The name of the Config_Error() function is misleading: it is not only
used to show configuraton errors, but all messages shown during normal
operation as well as for "config testing": it takes care of the correct
formatting of the messages (syslog, forground logging, config testing).

This fixes commit bb1d014abad8.

commit - 8a37695bf363a7cc2eb4bf3d17ff651f92cab253
commit + 8d414b079c1b4b0b8c88c8ab5cf4b27bf0942752
blob - d3743abf5a64e629f1a8e7294f31a283ffcd4699
blob + a58ac26e2c301cdb108e1350d3ac7b1e9aded0c4
--- src/ngircd/conf.c
+++ src/ngircd/conf.c
@@ -903,7 +903,7 @@ Read_Config(bool TestOnly, bool IsStarting)
 	FILE *fd;
 	DIR *dh;
 
-	Log(LOG_INFO, "Using configuration file \"%s\" ...", NGIRCd_ConfFile);
+	Config_Error(LOG_INFO, "Using configuration file \"%s\" ...", NGIRCd_ConfFile);
 
 	/* Open configuration file */
 	fd = fopen( NGIRCd_ConfFile, "r" );