summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZdenek Kabelac <zkabelac@redhat.com>2017-10-26 13:55:36 +0200
committerZdenek Kabelac <zkabelac@redhat.com>2017-10-26 14:04:58 +0200
commit837bfab75c712c28c161309f1381bb7a84eb17fb (patch)
tree22aba9a449f8ad6f86fc433c5601af4323896900
parent1758614f9648d4dfba91377336c60aaf3cc5265c (diff)
downloadlvm2-837bfab75c712c28c161309f1381bb7a84eb17fb.tar.gz
log: better message when reached log limit
Add explaining message, when command was aborted due to the reach of configure line number count (LVM_LOG_FILE_MAX_LINES) for logging (used mainly with testing).
-rw-r--r--lib/log/log.c11
1 files changed, 8 insertions, 3 deletions
diff --git a/lib/log/log.c b/lib/log/log.c
index 8ca60e4f9..c0789b456 100644
--- a/lib/log/log.c
+++ b/lib/log/log.c
@@ -646,11 +646,16 @@ static void _vprint_log(int level, const char *file, int line, int dm_errno_or_c
vfprintf(_log_file, trformat, ap);
va_end(ap);
+ if (_log_file_max_lines && ++_log_file_lines >= _log_file_max_lines) {
+ fprintf(_log_file, "\n%s:%d %sAborting. Command has reached limit "
+ "for logged lines (LVM_LOG_FILE_MAX_LINES=" FMTu64 ").",
+ file, line, _msg_prefix,
+ _log_file_max_lines);
+ fatal_internal_error = 1;
+ }
+
fputc('\n', _log_file);
fflush(_log_file);
-
- if (_log_file_max_lines && ++_log_file_lines >= _log_file_max_lines)
- fatal_internal_error = 1;
}
if (_syslog && (_log_while_suspended || !critical_section())) {