James Thomas Moon
James Thomas Moon
Same type of format from `/var/log/anaconda/X.log` ```text $ cat /var/log/anaconda/X.log [ 25.246] (WW) Failed to open protocol names file /usr/lib64/xorg/protocol.txt [ 25.247] X.Org X Server 1.20.11 X Protocol Version 11,...
Similar to Issue #13
The current code: https://github.com/jtmoon79/super-speedy-syslog-searcher/blob/0.0.32/src/readers/blockreader.rs#L932-L943 It uses https://github.com/gendx/lzma-rs/releases/tag/v0.2.0 The problem is due to `lzma-rs` crate not providing the uncompressed file size. But uncompressed file size must be known before `BlockReader::new` returns....
Another way this issue manifests is reading too many blocks for files without syslines. File `eipp.log.xz` has decompressed content like ```text Package: software-properties-common Architecture: all Version: 0.99.9.8 APT-ID: 71737 Status:...
- [ ] TODO Look into `lzma-rs` feature [_Expose a new raw_decoder API_](https://github.com/gendx/lzma-rs/blob/master/CHANGELOG.md#030---2023-01-04)
_Update: see Issue #283_ --- A good solution for this Issue and Issue #13 would be having a "_sequential read mode_" for `SyslogProcessor` that is also handed down to `SyslineReader`,...
Cannot read the xz file in chunks/blocks. The crate `lzma-rs` does not provide API `xz_decompress_with_options`. See https://github.com/gendx/lzma-rs/issues/110 Consider https://docs.rs/xz2/latest/xz2/read/struct.XzDecoder.html
#283 refactors handling `.xz`. However the problem remains of reading the entire file during an open.
File [`./logs/Windows10Pro/SoftwareDistribution/ReportingEvents.log`](https://github.com/jtmoon79/super-speedy-syslog-searcher/blob/0.5.58/logs/Windows10Pro/SoftwareDistribution/ReportingEvents.log) is UTF-16 encoded. Many ad-hoc Windows log files are encoded something not ASCII or UTF-8.
See design suggestion in https://github.com/jtmoon79/super-speedy-syslog-searcher/issues/285#issue-2254727678