Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,012
    • Issues 1,012
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #16568
Closed
Open
Issue created Mar 17, 2019 by intrigeri@intrigeriMaintainer

Make writing persistence.conf.bak more robust

Originally created by @intrigeri on #16568 (Redmine)

… as suggested on #16461 (comment 12566):

  • I’ve checked and indeed, it would make sense to sync that file after copying.
  • The chattr part is not needed as long as 1. t-p-s sync’s the file; 2. t-p-s is the only component that modifies that file (which is the case currently). But I guess it wouldn’t hurt and who knows, something else might start modifying that file at some point. Let’s do it.

Feature Branch: t-p-s:bugfix/16568-more-robust-backup, bugfix/16568-more-robust-backup

Parent Task: #10976 (closed)

Related issues

  • Related to #14544 (closed)
  • Related to #16461 (closed)
Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking