Hi,
I have a fedora15 x86_64 box with clamav-0.97.2, postfix-2.8.4, and
amavisd-new-2.6.6 with spamassassin-3.3.2 that has been running fine
for quite a while. Recently, clamd has died with an error similar to
this:
Oct 10 02:55:56 mail02 amavis[25696]: (25696-18) (!)run_av
(ClamAV-clamscan)
On 2011-10-10 10:24, Alex wrote:
Hi,
I have a fedora15 x86_64 box with clamav-0.97.2, postfix-2.8.4, and
amavisd-new-2.6.6 with spamassassin-3.3.2 that has been running fine
for quite a while. Recently, clamd has died with an error similar to
this:
Oct 10 02:55:56 mail02 amavis[25696]:
Hi,
I have a fedora15 x86_64 box with clamav-0.97.2, postfix-2.8.4, and
amavisd-new-2.6.6 with spamassassin-3.3.2 that has been running fine
for quite a while. Recently, clamd has died with an error similar to
this:
Oct 10 02:55:56 mail02 amavis[25696]: (25696-18) (!)run_av
On 2011-10-10 11:25, Alex wrote:
Hi,
I have a fedora15 x86_64 box with clamav-0.97.2, postfix-2.8.4, and
amavisd-new-2.6.6 with spamassassin-3.3.2 that has been running fine
for quite a while. Recently, clamd has died with an error similar to
Was it clamd that died or both clamd and
On 9/30/2011 9:37 PM, Rohler, Brian L wrote:
I have a large number of files (9TB) with over a million files and
thousands of directories. I would like to scan the group one time so
I have a good baseline. After that I would like to scan files that
are less than 365 days old. Can I use clamscan
Hi there,
On Mon, 10 Oct 2011 Matus UHLAR wrote:
luckily un*x filesystems have ctime (inode change time) which changes
everytime someone does this, so find can use -ctime option to get even
such files
However metadata support in some filesystems supported under un*x can be
patchy, and some
On 10/10/2011 4:42 AM, Török Edwin wrote:
On 2011-10-10 11:25, Alex wrote:
Is there a way to have it automatically restarted when something like
this happens or be more tolerant of database problems, with
notifications of those problems, in the future?
If bug 2727 is any indication, don't bet
On 10/10/2011 5:28 AM, Matus UHLAR - fantomas wrote:
On 9/30/2011 10:56 PM, Nathan Gibbs wrote:
clamscan itself isn't that smart, but if you are using unix, find could
feed a list of things to clamscan.
On 03.10.11 11:34, Bowie Bailey wrote:
Just keep in mind that it is quite easy to
Hi,
I have a fedora15 x86_64 box with clamav-0.97.2, postfix-2.8.4, and
amavisd-new-2.6.6 with spamassassin-3.3.2 that has been running fine
for quite a while. Recently, clamd has died with an error similar to
Was it clamd that died or both clamd and clamscan?
It looks like both:
Oct 10
Hi,
Is there a way to have it automatically restarted when something like
this happens or be more tolerant of database problems, with
notifications of those problems, in the future?
If bug 2727 is any indication, don't bet on it.
I don't think it's that bug, since I have a version greater
On 2011-10-10 19:15, Alex wrote:
Hi,
I have a fedora15 x86_64 box with clamav-0.97.2, postfix-2.8.4, and
amavisd-new-2.6.6 with spamassassin-3.3.2 that has been running fine
for quite a while. Recently, clamd has died with an error similar to
Was it clamd that died or both clamd and
On 2011-10-10 19:29, Alex wrote:
Hi,
Is there a way to have it automatically restarted when something like
this happens or be more tolerant of database problems, with
notifications of those problems, in the future?
If bug 2727 is any indication, don't bet on it.
I don't think it's that
On 10/10/2011 12:29 PM, Alex wrote:
Hi,
Is there a way to have it automatically restarted when something like
this happens or be more tolerant of database problems, with
notifications of those problems, in the future?
If bug 2727 is any indication, don't bet on it.
I don't think it's
On Mon Oct 10 2011 18:49:33 GMT+0200 (CEST)
Török Edwin ed...@clamav.net wrote:
Is there anything I should watch for, or do when it happens again? How
can I manually check the integrity of all the databases when it fails?
Run clamscan /dev/null (or any file), and it will print an error if
14 matches
Mail list logo
