Allows cf-ddns.py to open conf file from own directory#4
Open
anchepiece wants to merge 1 commit intoAmirAzodi:masterfrom
Open
Allows cf-ddns.py to open conf file from own directory#4anchepiece wants to merge 1 commit intoAmirAzodi:masterfrom
anchepiece wants to merge 1 commit intoAmirAzodi:masterfrom
Conversation
When running from cron, instead of changing the working directory to the script location, this commit will source the conf file from the script's own directory automatically.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When running from cron, instead of changing the working directory to the script location, this commit will source the conf file from the script's own directory automatically.
For example, if your crontab entry looks like this:
/home/user/bin/cf-ddns.py
you may get a file not found error
IOError: [Errno 2] No such file or directory: 'cf-ddns.conf'
Here we save the script location and then use that to build the patch to the conf file directly.
Hope this helps!