{"version":"2.1.257","anchor":"history-purge-now-uses-a-lock-and-detects-lock-compromise","canonical_anchor":"history-purge-now-uses-a-lock-and-detects-lock-compromise","heading":"History purge now uses a lock and detects lock compromise","tier":"notice","area":"Data Retention","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/history-purge-now-uses-a-lock-and-detects-lock-compromise","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### History purge now uses a lock and detects lock compromise\n\nHistory purges take a lock and refuse the rewrite if another process disturbs it mid-run.\n\nHistory purge and rewrite operations now acquire a lock before running, and detect if another process disturbs it mid-rewrite. If the lock is compromised, the rewrite is refused and reported as `History purge lock compromised` or `History purge (--all) lock compromised`.\n\n- Area: Data Retention\n- Names: `--all`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}