New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change working directory #2509
change working directory #2509
Conversation
When running as cron, pg_dump might complain about permissions in the current working directory. changing directory to the BACKUP_SCRIPT_PATH solves this.
Thanks for your contribution! As already mentioned in #2508 I personally don't see this as a real problem, as you should rather work with the crontab of the Zammad-User instead of root. I will therefor not merge this pull request, as I don't see the benefit (no offense!). |
@monotek I just saw that you reopened this PR. So you think we should merge it? What do we need to do next? |
closed by accident - re-open |
Optimized when we run the change dir, because we only need it if everything is good to go. I'll now add a remark internally so that I won't to it a fourth time.
@thorsteneckel this is ready for merging. :-) |
We currently can't merge PRs from Github, this is why I'm closing this PR for the sake of our internal MR no. 866 Thank you very much for your contribution! |
fixes #2508
When running as cron, pg_dump might complain about permissions in the current working directory.
changing directory to the BACKUP_SCRIPT_PATH solves this.