starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-09-02 18:47:21 +02:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

Add lockfile #8

New Issue
Closed
opened 2025-12-29 00:21:43 +01:00 by adam · 2 comments
adam commented 2025-12-29 00:21:43 +01:00
Owner
Copy Link
Copy Source

Originally created by @lukas2511 on GitHub (Dec 8, 2015).

If this script is used inside a cronjob it may interfere with a user using the script, so i think it would be a good idea to have some sort of lock-file to make sure it's at least not signing the same domain at the same time, or maybe even that it's not running at the same time.

Originally created by @lukas2511 on GitHub (Dec 8, 2015). If this script is used inside a cronjob it may interfere with a user using the script, so i think it would be a good idea to have some sort of lock-file to make sure it's at least not signing the same domain at the same time, or maybe even that it's not running at the same time.
adam closed this issue 2025-12-29 00:21:43 +01:00
adam commented 2025-12-29 00:21:44 +01:00
Author
Owner
Copy Link
Copy Source

@alexandresobolevski commented on GitHub (Feb 23, 2017):

Hi @lukas2511 . Could I ask you to elaborate on what exactly is protected. My situation is that I wish the script to be accessible asynchronously to renew certificates of some of my domains. It will be accessed from different processes - possibly at the same time but renewals are performed for different domains. What are the repercussions if I use the no-lock argument?
Thanks a lot.

@alexandresobolevski commented on GitHub (Feb 23, 2017): Hi @lukas2511 . Could I ask you to elaborate on what exactly is protected. My situation is that I wish the script to be accessible asynchronously to renew certificates of some of my domains. It will be accessed from different processes - possibly at the same time but renewals are performed for different domains. What are the repercussions if I use the `no-lock` argument? Thanks a lot.
adam commented 2025-12-29 00:21:44 +01:00
Author
Owner
Copy Link
Copy Source

@lukas2511 commented on GitHub (Mar 27, 2017):

@alexandresobolevski sorry for the late response: locking basically protects the script to write to the same files at the same time. if you register an account key first and control the script externally later on using the -d domain.tld -d www.domain.tld options there shouldn't be any remaining conflicts, but you should never use the no-lock option when running with a domains.txt

@lukas2511 commented on GitHub (Mar 27, 2017): @alexandresobolevski sorry for the late response: locking basically protects the script to write to the same files at the same time. if you register an account key first and control the script externally later on using the `-d domain.tld -d www.domain.tld` options there shouldn't be any remaining conflicts, but you should never use the no-lock option when running with a domains.txt
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complicated
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 suggestions wanted
testing
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#8