Hi,
When I updated to clamd 0.94 I got 2 messages that /etc/clamd and /etc/freshclam rpm had been changed to rpmnew.
Is clamd.conf.rpmnew and freshclam.conf.rpmnew the new files that were just installed or the old ones that were saved?
Should I copy the .rpmnew files over to the clamd.conf and freshclam.conf files.
For instance the freshclam.conf.rmpnew says:
DatabaseOwner clamav
But the freshclam.conf says:
DatabaseOwner qscand
This is confusing to me.
Thank you!
============
I found my other post about this and have mv clamd.conf.rpmnew and freshclam.conf.rpmnew to clamd.conf and freshclam.conf so hope this is correct...still not getting it.
clamd update 0.94 - need some understanding
ok ... I just noticed that the qmail-scanner.ini says:
# ClamAV settings
CLAMD_USER="qscand" # default is clamav
I should either change this or change the other 2 files back right?
Which setting is better for updates and such?
Also I checked /var/clamav and the owner and user was clamav clamav after the install.
# ClamAV settings
CLAMD_USER="qscand" # default is clamav
I should either change this or change the other 2 files back right?
Which setting is better for updates and such?
Also I checked /var/clamav and the owner and user was clamav clamav after the install.
-
breun
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
The rpmnew files are the new versions, but your old files were not automatically replaced, because they were modified (to use the qscand user instead of clamav, because qmail-scanner needs this modification).
My advice: apply the modification to the rpmnew files (change the user to qscand) and then copy the rpmnew file over the old one and then restart the service.
In my experience I need to do the following when a ClamAV update is available (this is from memory):
1. Update the packages using yum: yum update
2. If you get /etc/clamd.conf.rpmnew, change the User in the rpmnew to qscand, optionally backup the current clamd.conf and copy clamd.conf.rpmnew over clamd.conf.
3. If you get /etc/freshclam.conf.rpmnew, change DatabaseOwner in the rpmnew to qscand, optionally backup the current freshclam.conf and copy freshclam.conf.rpmnew over freshclamd.conf.
4. Fix ownership: chown -R qscand:qscand /var/clamav && chown -R qscand:qscand /var/log/clamav
5. Restart clamd: service clamd restart
6. Check if freshclam works: freshclam
7. Reconfigure qmail-scanner: qmail-scanner-reconfigure
You'll always need to deal with rpmnew files yourself when a default config file changes and you're using a modified version.
My advice: apply the modification to the rpmnew files (change the user to qscand) and then copy the rpmnew file over the old one and then restart the service.
In my experience I need to do the following when a ClamAV update is available (this is from memory):
1. Update the packages using yum: yum update
2. If you get /etc/clamd.conf.rpmnew, change the User in the rpmnew to qscand, optionally backup the current clamd.conf and copy clamd.conf.rpmnew over clamd.conf.
3. If you get /etc/freshclam.conf.rpmnew, change DatabaseOwner in the rpmnew to qscand, optionally backup the current freshclam.conf and copy freshclam.conf.rpmnew over freshclamd.conf.
4. Fix ownership: chown -R qscand:qscand /var/clamav && chown -R qscand:qscand /var/log/clamav
5. Restart clamd: service clamd restart
6. Check if freshclam works: freshclam
7. Reconfigure qmail-scanner: qmail-scanner-reconfigure
You'll always need to deal with rpmnew files yourself when a default config file changes and you're using a modified version.
Lemonbit Internet Dedicated Server Management
