On 05/26/2010 07:33 PM, Michael Feldmann wrote: > Am 26.05.2010 08:34, schrieb Török Edwin: >> On 05/25/2010 11:31 PM, Michael Feldmann wrote: >>> Yes it really seems like a memory problem. When I start clamd only with >>> the daily.cvd it starts without a problem, but adding the main.cvd >>> brings back the error. As I definitely do not have a chance of setting >>> up a swap file (the "swapon" returning "operation not permitted") I can >>> only hope that the clamAV engine will somehow sometime be rebuilt. >>> >> >> Did you check the ulimit settings? That doesn't require setting up a >> swapfile. > > > > This is the output: > > h830101:~ # ulimit -a > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > file size (blocks, -f) unlimited > max locked memory (kbytes, -l) 32 > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > stack size (kbytes, -s) unlimited > cpu time (seconds, -t) unlimited > max user processes (-u) 16375 > virtual memory (kbytes, -v) unlimited > h830101:~ # > > > Are there any values worth changing?
No, looks fine, I don't know why fork() fails. 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 Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
