[GH-ISSUE #6] Performing multiple changes to the DNS results in multiple copies of the updates #5

Closed
opened 2026-03-16 12:09:29 +03:00 by kerem · 1 comment
Owner

Originally created by @ndjdev on GitHub (Feb 16, 2016).
Original GitHub issue: https://github.com/HiddenClever/digitalocean-dns-sync/issues/6

Implement a lockfile system so if another instance of the script is due to run, don't add another sync in.

Originally created by @ndjdev on GitHub (Feb 16, 2016). Original GitHub issue: https://github.com/HiddenClever/digitalocean-dns-sync/issues/6 Implement a lockfile system so if another instance of the script is due to run, don't add another sync in.
kerem closed this issue 2026-03-16 12:09:34 +03:00
Author
Owner

@ndjdev commented on GitHub (Feb 17, 2016):

Fixed by adding a check_sync_scheduled function to the installer in @4aecc88670 @28dc048f96 @6b5ee9b407

<!-- gh-comment-id:185321219 --> @ndjdev commented on GitHub (Feb 17, 2016): Fixed by adding a check_sync_scheduled function to the installer in @4aecc88670fde66b510b1a11e866818fb45189aa @28dc048f969cb328b64b8da7838f78fe048e9388 @6b5ee9b407bb0f8ce450e08790915937e646c400
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/digitalocean-dns-sync#5
No description provided.