Re: [CentOS] ClamAV version(s)

2008-04-25 Thread John
On Thu, 2008-04-24 at 10:20 -0700, Paul Heinlein wrote:
 On Thu, 24 Apr 2008, Sam Drinkard wrote:
 
  I had clamav-milter working as well as clamd, then for some reason 
  clamd stopped and would not create the socket.  After much hair 
  pulling, I finally tracked the problem(s) down to /etc/clamd.conf.
 
 After enduring failed starts several times, I now just assume that the 
 ClamAV developers have changed configuration syntax any time there's a 
 version upgrade. I further assume that my configuration file will 
 contain obsolete or errant directives that will prevent the upgraded 
 clamd from starting.
 
 There's no such thing as a hands-off ClamAV upgrade. :-/


Why not? If you use all the current versions there is. yum remove what
you have or rpm -e what you have and Reinstall! Sort of hands off.
 
-- 
~/john

OpenPGP Sig:BA91F079

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] ClamAV version(s)

2008-04-25 Thread Barry Brimer

There's no such thing as a hands-off ClamAV upgrade. :-/


Why not? If you use all the current versions there is. yum remove what
you have or rpm -e what you have and Reinstall! Sort of hands off.


It *COULD* be a hands-off upgrade as long there are no upgrade notes 
listed at http://wiki.clamav.net/Main/UpgradeInstructions for the new 
version.  If there are notes about the version you are upgrading to, you 
can plan on clamd not starting after the upgrade until you modify your 
clamd.conf to account for the changes in the upgrade notes.


Barry
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] ClamAV version(s)

2008-04-25 Thread John
On Fri, 2008-04-25 at 07:57 -0500, Barry Brimer wrote:
  There's no such thing as a hands-off ClamAV upgrade. :-/
 
  Why not? If you use all the current versions there is. yum remove what
  you have or rpm -e what you have and Reinstall! Sort of hands off.
 
 It *COULD* be a hands-off upgrade as long there are no upgrade notes 
 listed at http://wiki.clamav.net/Main/UpgradeInstructions for the new 
 version.  If there are notes about the version you are upgrading to, you 
 can plan on clamd not starting after the upgrade until you modify your 
 clamd.conf to account for the changes in the upgrade notes.
 
 Barry
Just meant it as typical cander.
Not to hands on compared to some just change clam.conf.rpmnew to
clam.conf and be glad that all you have to do. Some things are a *pain*.
Look 3 days back for my post on clamav not upgrading.

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
-- 
~/john

OpenPGP Sig:BA91F079

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] ClamAV version(s)

2008-04-24 Thread Barry Brimer
Quoting Sam Drinkard [EMAIL PROTECTED]:

 I had clamav-milter working as well as clamd, then for some reason clamd
 stopped and would not create the socket.  After much hair pulling, I
 finally tracked the problem(s) down to /etc/clamd.conf.  After
 commenting all the stuff out that was providing errors, it is now
 working again.  I had somehow mixed versions from sourceforge and
 centos, and when I could not get things to update correctly, I removed
 clamav-milter and reinstalled it.  My question is about clamd.  clamd
 --version yields ClamAV 0.88.7/2314/Sun Dec 10 15:02:13 2006 

 Is this the most current version available from centos?  In the logs,
 there is a note about it being drastically outdated and pointed me to an
 FAQ file on clamd.  I don't want to go through that hassle of mixing
 repos and get all fouled up again.

The version you have is very outdated.  rpmforge has updated packages that work
well.  I highly recommend them.

Barry
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] ClamAV version(s)

2008-04-24 Thread Paul Heinlein

On Thu, 24 Apr 2008, Sam Drinkard wrote:

I had clamav-milter working as well as clamd, then for some reason 
clamd stopped and would not create the socket.  After much hair 
pulling, I finally tracked the problem(s) down to /etc/clamd.conf.


After enduring failed starts several times, I now just assume that the 
ClamAV developers have changed configuration syntax any time there's a 
version upgrade. I further assume that my configuration file will 
contain obsolete or errant directives that will prevent the upgraded 
clamd from starting.


There's no such thing as a hands-off ClamAV upgrade. :-/

--
Paul Heinlein  [EMAIL PROTECTED]  http://www.madboa.com/
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos