Ensure atomicity for lastsync file
This should take care of having empty lastsync files being served. Possible cause is that the IO is stuck thus taking several seconds to write the lastsync timestamp. This causes mirrors to download the empty file which causes checks to fail.
Merge request reports
Activity
mentioned in issue arch-mirrors#52 (closed)
- Resolved by pita strudl
- Resolved by pita strudl
added 151 commits
-
d6899989...d49c0b12 - 150 commits from branch
archlinux:master
- c24020a2 - Merge branch 'master' of https://gitlab.archlinux.org/archlinux/infrastructure
-
d6899989...d49c0b12 - 150 commits from branch
added 1 commit
- d8337b0f - dbscripts: Ensure atomicity of lastsync file
added 11 commits
-
d8337b0f...ed822cb3 - 10 commits from branch
archlinux:master
- ea56a87f - dbscripts: Ensure atomicity of lastsync file
-
d8337b0f...ed822cb3 - 10 commits from branch
added 4 commits
-
ea56a87f...2d9eee92 - 3 commits from branch
archlinux:master
- 1e5808d2 - dbscripts: Ensure atomicity of lastsync file
-
ea56a87f...2d9eee92 - 3 commits from branch
added 5 commits
-
1e5808d2...914e222c - 4 commits from branch
archlinux:master
- 96e4c4d6 - dbscripts: Ensure atomicity of lastsync file
-
1e5808d2...914e222c - 4 commits from branch
- Resolved by pita strudl
added 1 commit
- a645fa37 - dbscripts: Ensure atomicity of lastsync file
added 18 commits
-
a645fa37...914e222c - 17 commits from branch
archlinux:master
- df2e005b - dbscripts: Ensure atomicity of lastsync file
-
a645fa37...914e222c - 17 commits from branch
added 1 commit
- 7e118edd - dbscripts: Ensure atomicity of lastsync file
added 1 commit
- 84d3567a - dbscripts: Ensure atomicity of lastsync file
Please register or sign in to reply