Kir Kolyshkin 1e13f66fbb logger: fix follow logs for max-file=1 ... In case jsonlogfile is used with max-file=1 and max-size set, the log rotation is not perfomed; instead, the log file is closed and re-open with O_TRUNC. This situation is not handled by the log reader in follow mode, leading to an issue of log reader being stuck forever. This situation (file close/reopen) could be handled in waitRead(), but fsnotify library chose to not listen to or deliver this event (IN_CLOSE_WRITE in inotify lingo). So, we have to handle this by checking the file size upon receiving io.EOF from the log reader, and comparing the size with the one received earlier. In case the new size is less than the old one, the file was truncated and we need to seek to its beginning. Fixes #39235. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit 9cd24ba605) Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>		2019-09-23 11:29:52 -07:00
..
log_tag.go	Add canonical import comment	2018-02-05 16:51:57 -05:00
log_tag_test.go	Add canonical import comment	2018-02-05 16:51:57 -05:00
logfile.go	logger: fix follow logs for max-file=1	2019-09-23 11:29:52 -07:00
logfile_test.go	Use assert.NilError() instead of assert.Assert()	2019-01-21 13:16:02 +01:00