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

Make freshclam execution optionnable via attribute (even of debian/ubuntu) #52

Closed
lotooo opened this issue Jan 18, 2016 · 1 comment
Closed

Comments

@lotooo
Copy link

lotooo commented Jan 18, 2016

It is currently possible to use freshclam as a service the attribute node['clamav']['freshclam']['enabled'], which is great.

But if you are running a VM with paltform_family == 'debian' a freshclam execution is forced.

  if !node['clamav']['freshclam']['enabled'] || platform_family == 'debian'
    notifies :run, 'execute[freshclam]', :immediately
  end

Is there a reason why this is not 100% customizable via the attribute ? (something like default is true but if you are running debian the default is false). That way we can choose to force a freshclam refresh during the chef_run or not.

@lotooo
Copy link
Author

lotooo commented Jan 18, 2016

The goal is to avoid a long chef_run not to avoid the refresh, move this to :delayed instead of :immediatly should be enough.

lotooo pushed a commit to lotooo/clamav-chef that referenced this issue Jan 18, 2016
lotooo pushed a commit to lotooo/clamav-chef that referenced this issue Feb 2, 2016
…will be executed only if the attribute is set
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