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

cache_dir on mounted filesystem #108

Closed
jflorian opened this issue Oct 3, 2018 · 0 comments · Fixed by #116
Closed

cache_dir on mounted filesystem #108

jflorian opened this issue Oct 3, 2018 · 0 comments · Fixed by #116

Comments

@jflorian
Copy link

jflorian commented Oct 3, 2018

How does one go about having Puppet manage squid's cache_dir fully when it is to be on a separate filesystem. This module has squid::cache_dir which will create what will be the mount point, but if I want to have Puppet manage that mount I get into ordering problems. I cannot declare my own mount to occur before the squid class because the mount point may not exist yet or if I ensure it does, I'll have a duplicate declaration for it. If I declare the mount to occur after squid the mount point will exist so this can succeed but then it must notify => Class[squid`] (I believe) to actually start using it. This likely means restarting squid which seems sub-optimal. I guess that would only occur once during the initial setup so it's not terrible or is there a better way yet?

ralfbosz added a commit to ralfbosz/puppet-squid that referenced this issue Dec 28, 2018
Making it possible to create your own cache_dir
outside of the Squid module. Fixing issue voxpupuli#108.
ralfbosz added a commit to ralfbosz/puppet-squid that referenced this issue Jan 11, 2019
Making it possible to create your own cache_dir
outside of the Squid module. Fixing issue voxpupuli#108.
ralfbosz added a commit to ralfbosz/puppet-squid that referenced this issue Jan 11, 2019
Making it possible to create your own cache_dir
outside of the Squid module. Fixing issue voxpupuli#108.
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

Successfully merging a pull request may close this issue.

1 participant