You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: