• Bug#1094965: wtmpdb: provides no way to prune rotated logs

    From Andrew Bower@21:1/5 to All on Thu Apr 24 01:30:01 2025
    I have received some helpful feedback on this, essentially to the effect
    that the current policy is worse than useless because not only does it
    not prune but that the over-fragmented log files are just less useful.

    The suggestion is that rotation should either be disabled or given a
    long period like a year.

    I am inclined to agree with this suggestion, coupled with revised documentation.

    I also don't see a big reason why the logs couldn't be rotated with logrotate.d: there is no synchronisation issue that wtmpdb rotate
    solves. The sequence number for entries would restart but its
    monotonicity couldn't be relied upon anyway.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrew Bower@21:1/5 to All on Mon May 5 10:30:01 2025
    Control: tags -1 - patch

    Removing 'patch' tag.

    The proper approach needs better design - for both the rotation and
    pruning aspects. Even the directory used is questionnable.

    This issue is mitigated in 0.73.0-3 by disabling rotation by default on
    new installations.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)