logadm timestamps should not leak into the configfile
When using wildcard patterns in the configfile logadm will record the timestamps of all matched and rotated files in the timestamp file.
If the config file is then edited using
logadm -w or
logadm -r these timestamps can not be matched to existing rules in the configfile and will end up beeing written back into it.
This is confusing, especially when the patterns match many files and the configfile becomes huge.
Updated by Electric Monk about 2 years ago
- % Done changed from 80 to 100
- Status changed from In Progress to Closed
commit e911f24978ffe03577079badeef02cfc5e9aa296 Author: Sebastian Wiedenroth <email@example.com> Date: 2018-05-31T21:01:29.000Z 9556 logadm timestamps should not leak into the configfile Reviewed by: Toomas Soome <firstname.lastname@example.org> Reviewed by: Andy Fiddaman <email@example.com> Approved by: Robert Mustacchi <firstname.lastname@example.org>