From: Alexander Barton Date: Sun, 3 May 2020 15:08:51 +0000 (+0200) Subject: Correctly use Config_Error() instead of Log() in Read_Config() X-Git-Tag: rel-26-rc1~18 X-Git-Url: https://arthur.barton.de/gitweb/?p=ngircd.git;a=commitdiff_plain;h=8d414b079c1b4b0b8c88c8ab5cf4b27bf0942752 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. --- diff --git a/src/ngircd/conf.c b/src/ngircd/conf.c index d3743abf..a58ac26e 100644 --- a/src/ngircd/conf.c +++ b/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" );