diff options
| author | Micah <micah@leap.se> | 2016-04-18 21:58:06 -0400 |
|---|---|---|
| committer | Micah <micah@leap.se> | 2016-04-18 21:58:27 -0400 |
| commit | 2c5d27327bc1a90f5813e55a40d0acac644a13eb (patch) | |
| tree | 37e1d5beba7729b94148c57e4f8f230c6e343128 | |
| parent | 232047fdee815d9cf8c92b6853c5bc8039f2719c (diff) | |
Fix clamd start configuration (#8048)
If clamd is not running, the helpful cronjob tries to start it again,
but the way it is being started can only be run as root, and the cronjob
is run as the clamav user, so you get an error on each cron run. This
fixes that problem
Change-Id: I4cdb29dc651bee8a2eef1655ad4748d885afae0f
| -rw-r--r-- | puppet/modules/clamav/files/01-leap.conf | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/puppet/modules/clamav/files/01-leap.conf b/puppet/modules/clamav/files/01-leap.conf index abeeb302..a7e49d17 100644 --- a/puppet/modules/clamav/files/01-leap.conf +++ b/puppet/modules/clamav/files/01-leap.conf @@ -17,7 +17,7 @@ clamd_socket="/run/clamav/clamd.ctl" # shown above - if not enabled, then the following 2 variables will be # ignored, whether enabled or not. clamd_lock="/run/clamav/clamd.pid" -start_clamd="service clamav-daemon start" +start_clamd="clamdscan --reload" ss_dbs=" junk.ndb |