mirror of
https://github.com/boostorg/log.git
synced 2026-01-25 18:22:25 +00:00
f8954f6662
If the text file sink backend used the file that was previously scanned by file_collector as an old log file, on rotation the collector would store a duplicate of the file info. If the file was removed due to storage limits, the file info would still be stored despite the file being deleted. Also, in case if a file that is about to be rotated is deleted, don't hard fail with an exception. This may happen if another process have deleted the file or Boost.Log itself has. The latter can happen if multiple sinks write directly into the common target storage and one of them invokes file rotation, which due to the storage limits delete the file that is currently being written by the other sink.
