Use David's own (hopefully temporary mirror) which has the latest
rpm's. Search the archives back to June/July for the URL
announcement as I don't have it handy.
Fingers crossed RPMForge/Repoforge will sort their issues out soon.
been waiting too long - I have just migrated three mail servers from
repoforge versions of clam* to the epel versions - there are some items
to watch out for ....
steps if you have the amavis / spamassain / clamav setup as per centos wiki:
1. change repo priority or whatever so that yum update uses the epel version
2. copy freshclam.conf to save file and replace with freshclam.conf.rpmnew
3. copy clamd.conf to save file and replace with clamd.conf.rpmsave
4. mark up / edit any other changes you may have made to these files
(none in my case)
5. edit clamd.conf to change the sock file from
/var/run/clamav/clamd.sock to /var/run/clamav/clamd
6. add clam to the amavis group (epel uses user clam as opposed to
repoforge's clamd)
7. chown of the two current log files in /var/log/clamav/
8. restart clamd
check all working in logs, send some test emails and virus test
signatures ..... QED
YMMV
Kind Regards,
---------------------------
David Walsh
OntheNet - Senior Systems Engineer
P 07 5553 9222
F 07 5593 3557
www.OntheNet.com.au <http://www.OntheNet.com.au>
This e-mail and any attachments are private and confidential and may
contain privileged information. If you are notan authorised recipient,
the copying or distribution of this e-mail and any attachments is
prohibited and you mustnot read, print or act in reliance on this
e-mail or attachments. Any pricing information supplied via email is
anestimate or indicative only and may require a formal quotation to
verify full terms and conditions.
On 19 Feb 2014, at 8:55 am, rfusers <rfusers at okla.com
Post by rfusersClamav-0.98.1 had been out since 1/14/2014 and yet again no update is
available via repoforge.
Any ETA ?
--
This message has been scanned for viruses and
dangerous content by*MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean. _______________________________________________
users mailing list
users at lists.repoforge.org <mailto:users at lists.repoforge.org>
http://lists.repoforge.org/mailman/listinfo/users
_______________________________________________
users mailing list
users at lists.repoforge.org
http://lists.repoforge.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.repoforge.org/pipermail/users/attachments/20140219/d72bc366/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 4269 bytes
Desc: not available
URL: <
Loading Image...
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 4430 bytes
Desc: not available
URL: <
Loading Image...
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 4480 bytes
Desc: not available
URL: <
Loading Image...
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rkampen.vcf
Type: text/x-vcard
Size: 285 bytes
Desc: not available
URL: <http://lists.repoforge.org/pipermail/users/attachments/20140219/d72bc366/attachment-0001.vcf>
