Re: [Clamav-users] Central Management utility for CLAMAV on LINUX

2010-05-27 Thread Nathan Gibbs
* Rachamadagu, Vasu wrote:
 Hi,
 
 I am looking the feature of centrally manage the CLAMAV on Red Hat Linux
 for updating/pushing new virus definitions from one server to the other
 servers in enterprise environment.
 

Check the faq or mailing list archives for tiered updates or local mirror.
The basic idea is to use one freshclam to pull down the updates, make the
updated files accessible on an internal webserver, then point all the other
freshclams at it. To monitor your clamds, you could use clamdtop or

shameless-plug
clamd.monitor

http://cmpublishers.com/oss

Its designed to work with mon, but could be run from cron to watch your
installation.

/shameless-plug


-- 
Sincerely,

Nathan Gibbs

Systems Administrator
Christ Media
http://www.cmpublishers.com




signature.asc
Description: OpenPGP digital signature
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Re: [Clamav-users] Clamav Memory/System requirements

2010-05-27 Thread Shawn Bakhtiar



ps -aux

...
clamav2716  0.0  4.1 222492 168760 ?   Ssl  May26   0:40 clamd
clamav2722  0.0  0.0  57540   784 ?Ssl  May26   0:00 clamav-milter
...


On a Prolient GL165 4 x Quad-Core AMD Opteron(tm) Processor 2352 with 4GIG of 
memory. Fedora release 8 (Werewolf), ClamAV 0.96.1/11089/Thu May 27 06:47:23 
2010.


The process has been running for a day on our resides on our smtp gateway 
server, along side SpamAssassin..




 From: cswi...@mac.com
 Date: Wed, 26 May 2010 15:27:05 -0700
 To: clamav-users@lists.clamav.net
 Subject: Re: [Clamav-users] Clamav Memory/System requirements
 
 Hi, Alex--
 
 On May 26, 2010, at 3:04 PM, Alex wrote:
  Is it expected that clamd on Linux should take 315MB of RAM with a
  normal configuration? The system is pretty busy, with clamdtop being
  IDLE for no longer than two seconds at a time, with apparently three
  instances running.
 
 v0.96.1 clamd tends to run around 190MB during normal operation here under 
 FreeBSD, and can drop back to around 120 MB if left completely idle.   It 
 also tends to bounce up to nearly 300MB for a brief period when a DB refresh 
 happens, but it drops back to ~190MB pretty quickly
 
  Is that 315MB an accurate representation, as reported by clamdtop, and 
  standard top?
 
 Probably.  I gather that GNU's libc has deferred free() semantics when 
 threading is in use, so it might not be freeing up memory as quickly as other 
 C library implementations do.  You might also check that you don't have both 
 a main.cvd and main.cld, because that might cause two copies of the 
 signatures to get loaded and nearly double the memory requirements
 
  Is the memory requirements dependent upon the number of signatures, 
  databases, or otherwise?
 
 Mostly proportional to the # of signatures, which in my case is ~ 977401-- 
 plus some more if you scan big files.
 
 Regards,
 -- 
 -Chuck
 
 ___
 Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
 http://www.clamav.net/support/ml
  
_
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml


[Clamav-users] I did what you suggested. Then I get the following situation:, , , h830101:/etc # nohup /usr/local/sbin/clamd, [1] 19601, , [1]+ Stopped nohup /usr/loc

2010-05-27 Thread Michael Feldmann
Edwin,

I did what you suggested. Then I get the following situation:


 h830101:/etc # nohup /usr/local/sbin/clamd
 [1] 19601

 [1]+  Stopped nohup /usr/local/sbin/clamd
 h830101:/etc # ps axf|grep clam
 19601 pts/3T  0:00\_ nohup /usr/local/sbin/clamd
  h830101:/etc #

I cannot make anything out of this. Is the clamd running or not?

Mike
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml


Re: [Clamav-users] 0.96.1: Error: daemonize() fail

2010-05-27 Thread Michael Feldmann
Am 27.05.2010 07:46, schrieb Michael Feldmann.
I did what you suggested. Then I get the following situation:


 h830101:/etc # nohup /usr/local/sbin/clamd
 [1] 19601

 [1]+  Stopped nohup /usr/local/sbin/clamd
 h830101:/etc # ps axf|grep clam
 19601 pts/3T  0:00  \_ nohup /usr/local/sbin/clamd
 h830101:/etc #



I cannot make anything out of this. Is the clamd running or not?
Mike


 Am 26.05.2010 18:53, schrieb Török Edwin:

 Can you try setting 'Foreground yes' in clamd.conf and tell your init
 script to background clamd. I know Debian's init script has a
 'supervised' mode which allows for this, OpenSUSE should have something
 similar.

 --Edwin
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml


Re: [Clamav-users] I did what you suggested.

2010-05-27 Thread Török Edwin
On 05/27/2010 07:02 PM, Michael Feldmann wrote:
 Edwin,

Hi,

Please put the reply in the mail body, and not the subject.

 
 I did what you suggested. Then I get the following situation:
 
 
 h830101:/etc # nohup /usr/local/sbin/clamd
 [1] 19601

 [1]+  Stopped nohup /usr/local/sbin/clamd
 h830101:/etc # ps axf|grep clam
 19601 pts/3T  0:00\_ nohup /usr/local/sbin/clamd
 h830101:/etc #
 
 I cannot make anything out of this. Is the clamd running or not?

Looks like clamd stopped, that usually happens with terminal output.
Shouldn't happen with nohup though.

Type 'fg' to bring it to foreground, and see why it stopped.

--Edwin
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml


Re: [Clamav-users] 0.96.1: Error: daemonize() fail

2010-05-27 Thread Michael Feldmann
Am 26.05.2010 08:34, schrieb Török Edwin:

Looks like clamd stopped, that usually happens with terminal output.
Shouldn't happen with nohup though.

Type 'fg' to bring it to foreground, and see why it stopped.

I did so, here is the result:

===

h830101:/etc # nohup /usr/local/sbin/clamd 
[1] 9227

[1]+  Stopped nohup /usr/local/sbin/clamd
h830101:/etc # fg
nohup /usr/local/sbin/clamd
nohup: appending output to `nohup.out'



And the contents of nohup.out show nothing suspicious:


h830101:/etc # cat nohup.out
Limits: Global size limit set to 104857600 bytes.
Limits: File size limit set to 26214400 bytes.
Limits: Recursion level limit set to 16.
Limits: Files limit set to 1.
Limits: Core-dump limit is 0.
Archive support enabled.
Algorithmic detection enabled.
Portable Executable support enabled.
ELF support enabled.
Mail files support enabled.
OLE2 support enabled.
PDF support enabled.
HTML support enabled.
Self checking every 600 seconds.
Listening daemon: PID: 9227
MaxQueue set to: 100
Client disconnected (FD 14)
h830101:/etc #

=

Thanks again for your attempts to help
Mike
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml