Skip to content
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

/etc/condor/config.d/00_config_local.config.bak.$now is loaded #103

Open
sferry opened this issue Jan 17, 2019 · 1 comment
Open

/etc/condor/config.d/00_config_local.config.bak.$now is loaded #103

sferry opened this issue Jan 17, 2019 · 1 comment

Comments

@sferry
Copy link

sferry commented Jan 17, 2019

Hi,
There is this feature of keeping a copy of the last config file for
/etc/condor/config.d/27_shared_port.config
and
/etc/condor/config.d/00_config_local.config
appending a .bak.$now to the name of the file.
The problem is - if I got it right - that the file is actually loaded AFTER the new file (without the .bak.$now), hence there is no modification of the configured variables in condor ( only new variables are added).
The catch is that puppet Filebucketed the files and compute/compare the checksums and at the next run remove the .bak.$now file.

I beleive it is not recommended to have this behavior : "necessity to run twice the puppet agent to get the righ config".
Would it be possible to remove the 2 lines "backup => " ?
or
make sure the *.bak.$now are NOT loaded to condor.
Thanks
Sophie

@ccnifo
Copy link
Collaborator

ccnifo commented Dec 11, 2019

I think this was addressed in #120 for one of them (/etc/condor/config.d/00_config_local.config). Would you like to submit such a PR for 27_shared_port.config? I did not look closely to this issue, but it seems there's no good reason to keep this last "backup" file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants