Re: [vps-mail] ClamAV Questions

[Abigail Marshall <abigailrm@xxxxxxxxx>]

Any possibility of a vinstall coming soon on this?? The problem is
that when we do ports installations over a vinstall, or later try to
do a vinstall over a ports with programs - we tend to run into various
issues.  I'm comfortable with ports, but would rather keep things
consistent.

John, was your previous installation done with a vinstall? If so, were
there any issues or problems to be aware of in doing the ports
installation?

-Abigail

On 5/2/05, John Oligario <joligario@xxxxxxxxxxxxxxx> wrote:
> You should download and install 0.84, can be done via the ports, etc.  I
> recommend doing this ASAP.  I upgraded mine yesterday.
> 
> -----Original Message-----
> From: Matt Cohen [mailto:lists@xxxxxxxxxx]
> Sent: Monday, May 02, 2005 4:48 PM
> To: vps-mail@xxxxxxxxxxxx
> Subject: [vps-mail] ClamAV Questions
> 
> I've been pretty proud of ClamAV and what its been catching, which so far
> has been everything.
> 
> Until today - actually I think it started last night but there's a new Virus
> going around (news to me) that uses ZIP files and has been getting thru
> ClamAV as clean.
> 
> It was still getting through this morning so I thought i'd run freshclam to
> make sure the virus DB was being updated.  Here's what I
> got:
> 
> # /usr/local/bin/freshclam
> ClamAV update process started at Mon May  2 13:37:43 2005 Reading CVD header
> (main.cvd): OK main.cvd is up to date (version: 31, sigs: 33079, f-level: 4,
> builder: tkojm)
> WARNING: Your ClamAV installation is OUTDATED - please update immediately !
> WARNING: Current functionality level = 2, required = 4 Reading CVD header
> (daily.cvd): OK daily.cvd is up to date (version: 863, sigs: 973, f-level:
> 4, builder: diego)
> WARNING: Your ClamAV installation is OUTDATED - please update immediately !
> WARNING: Current functionality level = 2, required = 4
> 
> This got me a little concerned, so I did a vinstall of ClamAv. Aside from
> the odd message about unlinking my 'personal copy' of Clamav and using the
> system copy, that seemed to go fine.  (I picked the 'clamd'
> & 'clamdscan' option, and thank you to Scott or whomever is responsible for
> the vinstall for the great explanation of why I would want one or the other)
> 
> Then tried it again and got this:
> 
> # /usr/local/bin/freshclam
> ClamAV update process started at Mon May  2 13:46:37 2005
> WARNING: Your ClamAV installation is OUTDATED - please update immediately!
> WARNING: Local version: 0.83 Recommended version: 0.84 main.cvd is up to
> date (version: 31, sigs: 33079, f-level: 4, builder: tkojm) daily.cvd is up
> to date (version: 863, sigs: 973, f-level: 4, builder: diego)
> 
> While this error message seems less scary, i'm still a little concerned -
> should I be?
> 
> Thanks,
> Matt
> --
> :-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+
> Matthew I. Cohen                                   http://www.iwbyte.com/
> It Won't Byte Web Design & Hosting.     Ob. Quote: "Reality is for those
> email: lists@xxxxxxxxxx                  people who can't handle Fantasy"
> ======================================================================
> This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
> Before posting a question, please search the archives (see above URL).
> 
> ======================================================================
> This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
> Before posting a question, please search the archives (see above URL).
>

======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).