Hi
First things first. Do your backups.
When rebuilding clamav from source, be sure to set where the binary
will be located. Some   builds differ from the default RPM in where
they place the binary.


On Tue, 15 Mar 2005 08:52:55 +0300, Simon Vass <[EMAIL PROTECTED]> wrote:
> Hi William,
> 
> > Is your initial installation rpm based or not. If it is not rpm based, how
> did you upgrade and what should I look out for when upgrading?
> 
> No it was based on the most current version at the time which was 0.73 I
> think. But since then I have in place upgraded it to 0.80,81,82 and finally
> 83 without fuss. I just rebuild clamav from the source tgz once the new
> stable version appears. I usually test it on my desktop machines first
> before uploading it the servers I am responsible for. I would look out for
> problems with the .conf file maybe being overwritten and pointing to the
> wrong, but if you originally compiled from the source tgz I don't think this
> will be a problem.
> 
> Apart from that maybe just Item 4 on the clamav.net faq ;-)
> http://www.clamav.net/faq.html#pagestart
> 
> > This is a critical machine and I have almost zero room for errors(at least
> those that would interrupt the mail functions it is performing).
> 
> Any chance then of getting another machine, to rebuild in the image of the
> production server and test this out? Would be a good disaster recovery
> practise.
> 
> 
> Simon
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Lule George William
> Sent: 14 March 2005 16:16
> To: [email protected]
> Subject: RE: [LUG] Updating clamAV
> 
> Hello all,
> Allow me to answer both Mark and Simon in this mail.
> For Mark: The OS is SuSE 7.2 Kernel 2.4.4-4GB
> 
> > Hi William,
> >
> > In all honesty I would find a way to upgrade the antivirus.
> 
> Sure Simon, and there are some I came across, but as earlier mentioned, all
> were outlining upgrading procedures for rpm based installations, not tar.gz
> installations.
> 
> >I just upgraded
> > to 0.83 on Mandrake 10 and it is running fine.
> 
> Is your initial installation rpm based or not. If it is not rpm based, how
> did you upgrade and what should I look out for when upgrading?
> This is a critical machine and I have almost zero room for errors(at least
> those that would interrupt the mail functions it is performing).
> 
> > They seem to do this from time to time to force you to upgrade as
> >often they  are fixing security bugs.
> 
> Great.
> 
> >Is Mailscanner locked to 0.7 or any version?
> >
> 
> Nothing of that sort is mentioned in its documentation.
> 
> > Simon
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of
> > Lule George William
> > Sent: 14 March 2005 15:12
> > To: [email protected]
> > Subject: [LUG] Updating clamAV
> >
> > Hello all,
> > I have clamAV 0.70 on my main mail server, but this morning when I
> run
> > freshclam, I got the following error(it will be shown shortly). On
> googling,
> > I got to know that it is brought about because a newer version of
> clamAV is
> > available (cool!) but all the ways of updating that I found out were
> for rpm
> > based installations. Unfortunately for me, I used the tar.gz from
> clamav.net
> > and so far all indicators are for a re-install. Now I wouldn't like
> to
> > tinker with this system so I am wondering whether anyone has had
> this
> > problem before and could give me some guidelines on how to proceed.
> My
> > worries are further compounded by the fact that I am also running a
> tar.gz
> > installation of MailScanner that is relying on this clamAV
> installation! Any
> > suggestions?
> >
> > The error is here below:
> >
> > ===========================Begin error message======================
> > postmaster1:~ # freshclam ClamAV update process started at Mon Mar
> 14
> > 14:38:21 2005 SECURITY WARNING: NO SUPPORT FOR DIGITAL SIGNATURES
> Connecting
> > via xxx.xxx.xxx.xxx Reading CVD header (main.cvd): OK main.cvd is up
> to date
> > (version: 30, sigs: 31086, f-level: 4, builder:
> > tkojm)
> > WARNING: Your ClamAV installation is OUTDATED - please update
> immediately !
> > WARNING: Current functionality level = 2, required = 4 Connecting
> via
> > xxx.xxx.xxx.xxx Reading CVD header (daily.cvd): OK daily.cvd is up
> to date
> > (version: 762, sigs: 520, f-level: 4, builder:
> > ccordes)
> > WARNING: Your ClamAV installation is OUTDATED - please update
> immediately !
> > WARNING: Current functionality level = 2, required = 4 postmaster1:~
> #
> > ========================End of error================================
> >
> >
> ************************************************************************
> > Lule George William (Mr)
> > Network and Systems Administrator
> > Cisco Program Co-ordinator
> > Uganda Martyrs University, Nkozi
> > P.O. Box 5498 Kampala
> > Uganda
> > /* If you are not living and learning, then you are dumb and dying*/
> > _______________________________________________
> > LUG mailing list
> > [email protected]
> > http://kym.net/mailman/listinfo/lug
> > %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
> >
> >
> >
> 
> ************************************************************************
> Lule George William (Mr)
> Network and Systems Administrator
> Cisco Program Co-ordinator
> Uganda Martyrs University, Nkozi
> P.O. Box 5498 Kampala
> Uganda
> /* If you are not living and learning, then you are dumb and dying*/
> _______________________________________________
> LUG mailing list
> [email protected]
> http://kym.net/mailman/listinfo/lug
> %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
> 
> _______________________________________________
> LUG mailing list
> [email protected]
> http://kym.net/mailman/listinfo/lug
> %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
> 


-- 
Jean-Francois Laforest
Senior Network Engineer
Wavexpress, Inc.
_______________________________________________
LUG mailing list
[email protected]
http://kym.net/mailman/listinfo/lug
%LUG is generously hosted by INFOCOM http://www.infocom.co.ug/

Reply via email to