Follow log_level even when using journald output

fix #3328
This commit is contained in:
louiz’
2018-01-12 20:08:15 +01:00
parent 34d6c2bce1
commit b4b9828de5
2 changed files with 13 additions and 8 deletions
+2
View File
@@ -10,6 +10,8 @@ Version 7.0
would ignore our messages entirely. would ignore our messages entirely.
- Fix the iq result sent at the end of a MAM response. Some clients (e.g. - Fix the iq result sent at the end of a MAM response. Some clients (e.g.
gajim) would throw an error as a result. gajim) would throw an error as a result.
- log_level configuration option is no longer ignored if the logs are written
into journald
Sqlite3 to PostgreSQL migration Sqlite3 to PostgreSQL migration
------------------------------- -------------------------------
+4 -1
View File
@@ -74,8 +74,8 @@ public:
bool use_systemd{false}; bool use_systemd{false};
#endif #endif
private:
const int log_level; const int log_level;
private:
std::ofstream ofstream{}; std::ofstream ofstream{};
std::ostream stream; std::ostream stream;
@@ -105,6 +105,8 @@ namespace logging_details
if (Logger::instance()->use_systemd) if (Logger::instance()->use_systemd)
{ {
(void)level; (void)level;
if (level >= Logger::instance()->log_level)
{
std::ostringstream os; std::ostringstream os;
log(os, std::forward<U>(args)...); log(os, std::forward<U>(args)...);
sd_journal_send("MESSAGE=%s", os.str().data(), sd_journal_send("MESSAGE=%s", os.str().data(),
@@ -113,6 +115,7 @@ namespace logging_details
"CODE_LINE=%i", line, "CODE_LINE=%i", line,
nullptr); nullptr);
} }
}
else else
{ {
#endif #endif