summaryrefslogtreecommitdiffstats
path: root/tests/timestamp.sh
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2010-12-17 18:18:57 +0100
committerRainer Gerhards <rgerhards@adiscon.com>2010-12-17 18:18:57 +0100
commit50855878062dbcf8d2861ea169d3ca686c65b23b (patch)
treed1baedc207c6adadb3f18501c8ffd49508b1b936 /tests/timestamp.sh
parent371a8eec29fa25bbf58f4b1f0d7e3bf4c3ad6329 (diff)
downloadrsyslog-50855878062dbcf8d2861ea169d3ca686c65b23b.tar.gz
rsyslog-50855878062dbcf8d2861ea169d3ca686c65b23b.tar.xz
rsyslog-50855878062dbcf8d2861ea169d3ca686c65b23b.zip
bugfix: imfile potentially duplicates lines
This can happen when 0 bytes are read from the input file, and some writer appends data to the file BEFORE we check if a rollover happens. The check for rollover uses the inode and size as a criterion. So far, we checked for equality of sizes, which is not given in this scenario, but that does not indicate a rollover. From the source code comments: Note that when we check the size, we MUST NOT check for equality. The reason is that the file may have been written right after we did try to read (so the file size has increased). That is NOT in indicator of a rollover (this is an actual bug scenario we experienced). So we need to check if the new size is smaller than what we already have seen!
Diffstat (limited to 'tests/timestamp.sh')
0 files changed, 0 insertions, 0 deletions