On Wed, 09 Mar 2005 13:26:18 +1100
John Egan <[EMAIL PROTECTED]> wrote:
> Hi
>
> The above link failed
Fortunately,
--
oo. Tomasz Kojm <[EMAIL PROTECTED]>
(\/)\. http://www.ClamAV.net/gpg/tkojm.gpg
\..._ 0DCA5A08407D5288279DB43454822DC8
I noticed that at least with clamscan 0.83 that when scanning large files
such as .iso cd image files, sometimes memory consumption of the clamscan
process grows to ridiculous levels (as in, hundreds of megabytes). This
isn't filesystem cache or buffers, but actual memory consumed by this
proc
On Wed, 9 Mar 2005 08:23:53 -0500 (EST)
"Calin A. Culianu" <[EMAIL PROTECTED]> wrote:
> I could send an interested developer a .iso image that can
> consistently reproduce the problem..
No, thanks. Please post the output of clamscan --debug instead. If it's
big please only send it to bugs at cla
On Wednesday 09 Mar 2005 13:23, Calin A. Culianu wrote:
>
> I noticed that at least with clamscan 0.83 that when scanning large files
> such as .iso cd image files, sometimes memory consumption of the clamscan
> process grows to ridiculous levels (as in, hundreds of megabytes).
Is the current
Good question. I will try it and let you know.. :/
On Wed, 9 Mar 2005, Nigel Horne wrote:
On Wednesday 09 Mar 2005 13:23, Calin A. Culianu wrote:
I noticed that at least with clamscan 0.83 that when scanning large files
such as .iso cd image files, sometimes memory consumption of the clamscan
proc
I can confirm this happens with ClamAV devel-20050309 (the latest
snapshot just freshly compiled).
I have a 'top' screenshot to prove I am not crazy. I also have --debug
output.. and can even do more with gdb if need be.. :)
Any insights?
BTW, the memory consumption peak coin
I'm having two pretty persistent problems with clamav. The first is that
clamav is complaining about my version being out of date:
WARNING: Your ClamAV installation is OUTDATED - please update immediately!
WARNING: Your ClamAV installation is OUTDATED - please update immediately!
WARNING: Local v
On Wed, 9 Mar 2005 09:54:22 -0500 (EST)
"Jerry Bell" <[EMAIL PROTECTED]> wrote:
> trace of 0.81. But still it keeps happening! What am I missing?
A properly installed new version. Read the archives of this list.
> The database directory is /var/db/clamav. The permissions as as such:
Does it ma
> A properly installed new version. Read the archives of this list.
I've done so, and there are a lot of "what does this mean", and a fair
number of people who have half installed old versions. I don't think that
is the case for me.
When I start up freshclam, I see this:
freshclam daemon 0.83 (O
On Wed, 9 Mar 2005 10:26:52 -0500 (EST)
"Jerry Bell" <[EMAIL PROTECTED]> wrote:
> It seems clear to me that I've got the right version, but SOMETHING is
You've got the right version using old libs. Search the archives.
--
oo. Tomasz Kojm <[EMAIL PROTECTED]>
(\/)\.
Jerry Bell said:
>> A properly installed new version. Read the archives of this list.
>
> I've done so, and there are a lot of "what does this mean", and a fair
> number of people who have half installed old versions. I don't think that
> is the case for me.
Jerry - somewhere in your library path
On 8 Mar 2005 at 8:53, Trog wrote:
> On Tue, 2005-03-08 at 11:50 +0300, Jijos wrote:
> > it is updated to 0.83
> > it saying in rpm -q clamav is 0.83
> > i don't want to uninstall the exsiting one it is intergrated with my
> > mail server so i want to update it to 0.83 i updated it i want to
> > c
Since this problem show up so often isn't it a idea to take care of with a
software solution instead of telling the user to search the archives?
Ok, you can argue that it is not a fault in the software and the users own
fault but since it happens so often it might be good support to take care of
On Wed, 9 Mar 2005, Johan Barelds wrote:
> Since this problem show up so often isn't it a idea to take care of with a
> software solution instead of telling the user to search the archives?
I haven't run into this myself, but I have to say I've only seen this issue
come on the the Clam list.
N
Thank you for the detail here. Unfortunately, I had already done much of
that. ldd confirms that both clamd and freshclam are linked to
/usr/local/lib/libclamav.so.1
When I shut down clamd and freshclam, move that library out, and try to
restart, both clamd and freshclam bomb out saying the libr
On Wed, 2005-03-09 at 13:47 -0500, Jerry Bell wrote:
> Likewise, I have run strings on all libraries in /usr/local/lib and
> /usr/lib looking for the string 0\.81 and have only found
> /usr/local/lib//usr/local/lib/libclamav.so.1.
Are you running under a chroot() somewhere?
-trog
signature.as
Hi Dear Members!
i have seccessfuly configure clamav+qmail scaner on
solaris 8 intel.
when i use
./test_instaltion.sh doit
i got these line ...
QMAILQUEUE was not set, defaulting to
/var/qmail/bin/qmail-scanner-queue.pl for
this test...
Sending standard test message - no viruses...
>
> Since this problem show up so often isn't it a idea to take care of with a
> software solution instead of telling the user to search the archives?
>
> Ok, you can argue that it is not a fault in the software and the users own
> fault but since it happens so often it might be good support to
>
> Thank you for the detail here. Unfortunately, I had already done much of
> that. ldd confirms that both clamd and freshclam are linked to
> /usr/local/lib/libclamav.so.1
And yet the problem exists. My self analysis when this happens is to assure
myself that something I am certain of is wron
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jerry Bell
> Sent: woensdag 9 maart 2005 19:48
> To: ClamAV users ML
> Subject: Re: [Clamav-users] Two persistent problems with clamav
>
>
> Thank you for the detail here. Unfortunately, I had alread
> I have it working flawlessly on FreeBSD, too; so I know it works. :)
I don't doubt at all that the problem is on my end. I just for the life
of me can't figure out what it is. I've been doing this kind of thing for
a long long time and it's just not apparent to me what the problem is.
Normall
On March 9, 2005 11:44 am, Jerry Bell wrote:
> > find -X / -name "libclamav.so.1" | xargs ls -la
> No luck there :(
> >> /usr/local/lib//usr/local/lib/libclamav.so.1.
> That is what you call a careless cut and paste. It is really
> /usr/local/lib/libclamav.so.1
> I would have expected *some* tr
On Wed, 9 Mar 2005, Jerry Bell wrote:
> I would have expected *some* trace of an old lib somewhere. I can't find
> anything anywhere that has a version number of 0.81.
It's not going to say 0.81 (not in the file name, at least).
Ie: on my system, in /usr/local/lib I have:
-rw-r--r--1 root
>> I have it working flawlessly on FreeBSD, too; so I know it works. :)
>
> I don't doubt at all that the problem is on my end. I just for the life
> of me can't figure out what it is. I've been doing this kind of thing for
> a long long time and it's just not apparent to me what the problem is.
Jerry Bell wrote:
[snip]
When I start up freshclam, I see this:
freshclam daemon 0.83 (OS: freebsd5.2.1, ARCH: i386, CPU: i386)
ClamAV update process started at Wed Mar 9 10:06:35 2005
main.cvd is up to date (version: 30, sigs: 31086, f-level: 4, builder: tkojm)
daily.cvd is up to date (version: 7
>
>
> >> I have it working flawlessly on FreeBSD, too; so I know it works. :)
> >
> > I don't doubt at all that the problem is on my end. I just for the life
> > of me can't figure out what it is. I've been doing this kind of thing for
> > a long long time and it's just not apparent to me what
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> René Berber
> Sent: woensdag 9 maart 2005 21:02
> To: clamav-users@lists.clamav.net
> Subject: [Clamav-users] Re: Two persistent problems with clamav
>
>
> How do you start freshclam, as daemon or man
> How do you start freshclam, as daemon or manually to test it?
It's sztarted as a daemon by a script. I have manually started it up with
the same results.
>
> I don't agree with the library theory, it looks to me that you are
> running at least two different copies of freshclam, one of them is t
> It's not going to say 0.81 (not in the file name, at least).
That's correct. I was checking by grepping the "strings" output from each
of the files. Here are my libraries:
-rw-r--r-- 1 root wheel 365010 Mar 4 14:59 /usr/local/lib/libclamav.a
lrwxr-xr-x 1 root wheel 14 Mar 4 14:59
> That sounds very plausible to me. :) Clever thinking. It might also
> account for his permission problems (as the cron environment for that user
> may differ). Trying "crontab -u clamav -l" might prove quite revealing. :)
>
I can say for certain that I did not put it into cron, and I have verif
On March 9, 2005 01:33 pm, Jerry Bell wrote:
> > How do you start freshclam, as daemon or manually to test it?
>
> It's sztarted as a daemon by a script. I have manually started it up
> with the same results.
>
> > I don't agree with the library theory, it looks to me that you are
> > running at l
Freddie Cash wrote:
[snip]
Looking at the log output, it looks like you have two separate processes
running. One that wakes up every 30 minutes at 22 after and 52 after.
The other that wakes up at half-past (at least, there's not enough log
output to confirm the pattern). The entries are very
René Berber wanted us to know:
>I agree with this, the log shows two different processes running, both
>as daemon.
>Could the start script run freshclam twice?
No, when he upgraded from 0.81 to 0.83, it looks like the old process
was never killed. It happily kept running.
--
Regards...
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> René Berber
> Sent: woensdag 9 maart 2005 23:52
> To: clamav-users@lists.clamav.net
> Subject: [Clamav-users] Re: Two persistent problems with clamav
>
>
> I agree with this, the log shows two dif
> >
> > Could the start script run freshclam twice?
>
> Or could /usr/local/etc/rc.d/ contain two differently named
> startup scripts? That would do it, too. :)
>
> - Mark
Lacking any other problem, one of the two has to launch an earlier version
of the tool in order to generate the error shown
>
> René Berber wanted us to know:
>
> >I agree with this, the log shows two different processes running, both
> >as daemon.
> >Could the start script run freshclam twice?
>
> No, when he upgraded from 0.81 to 0.83, it looks like the old process
> was never killed. It happily kept running.
> -
It appears this was the case. I knew it was going to be something so
completely simple that I would be shamed from the list for a while, but I
was so far in the forest, I couldn't see the trees anymore.
BTW, I have no idea how that happened. I am pretty diligent about
shutting things down before
Jerry Bell said:
> It appears this was the case. I knew it was going to be something so
> completely simple that I would be shamed from the list for a while, but I
> was so far in the forest, I couldn't see the trees anymore.
Fehh - like we all haven't been there before. Have a beer on me -
hopef
Dear All,
I installed Clamav on my server. The log file
size is keep on increasing and it becomes huge in size.
How to clear ClamAV logs?
Thanks & RegardsLadhaSoftware
EngineerDevelopment TeamChennai,
India.
___
http://lurker.clamav.net/list/cl
On Thu, 10 Mar 2005 13:11:21 +0530, ladha <[EMAIL PROTECTED]> wrote:
>
> Dear All,
>
> I installed Clamav on my server. The log file size is keep on increasing
> and it becomes huge in size.
> How to clear ClamAV logs?
Use whatever software (newsyslog, logrotate, etc) that came with your
I am using the following command to rotate the log files.
/usr/sbin/logrotate -f /etc/logrotate.conf
But it is not cleaning the "clam-update.log" file
- Original Message -
From: "Rob MacGregor" <[EMAIL PROTECTED]>
To: "ClamAV users ML"
Sent: Thursday, March 10, 2005 1:09 PM
Subject: R
41 matches
Mail list logo
