thank a lot, you give me a great hint
from init script (at tarball contrib/init/RedHat), it seem set 'ulimit'
value
....
start() {
echo -n $"Starting $prog: "
# Don't allow files larger than 20M to be created, to limit DoS
# Needs to be large enough to extract the signature files
ulimit -f 20000
LANG= daemon $progdir/$prog
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/clamd
return $RETVAL
}
....
after set the 'ulimit' value larger than 'Global size limit' from clamd.log
Limits: Global size limit set to 104857600 bytes.
the message gone away.
After check the init script at FC3 machine, it hadn't 'ulimit' setting.
Thank for helping.
Török Edwin wrote:
>
> On 2008-11-18 03:12, martinnitram wrote:
>> both FC3 i386 and Fedora 8 x64 shown "unlimited".
>>
>> one more thing, before F8 x64 is running clamav rpm from offical yum repo
>> (latest version is 0.92-4), which hadn't shown this message.
>>
>> Thank again.
>>
>
> Check your init scripts, they usually set some ulimit. Put a call to
> ulimit -a just before calling clamd in your init script to see.
> Try running clamd directly (/usr/sbin/clamd), does it still show that
> message?
>
> Best regards,
> --Edwin
> _______________________________________________
> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
> http://www.clamav.net/support/ml
>
>
--
View this message in context:
http://www.nabble.com/what-is-the-meaning-of-%22System-limit-for-file-size-is-lower-than-maxfilesize-or-maxscansize%22-tp20534062p20555944.html
Sent from the clamav-users mailing list archive at Nabble.com.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
