This bug appears because of the way we get conf parameters values, for LogFile:
grep '^LogFile' /etc/clamav/clamd.conf LogFileMaxSize 0 LogFile /var/log/clamav/clamav.log LogFileUnlock false LogFileMaxSize 0
The fix:
diff clamav-daemon.postinst /var/lib/dpkg/info/clamav-daemon.postinst 175c175 < value=`grep "^$variable[[:space:]]" $CLAMAVCONF | head -n1 | awk '{print $2}'` --- > value=`grep ^$variable $CLAMAVCONF | head -n1 | awk '{print $2}'`
Test: < + grep ^LogFile /etc/clamav/clamd.conf < + value=0 < + [ -z 0 ] < + [ 0 != LogFile ] < + export LogFile=0 --- > + awk {print $2} > + grep ^LogFile[[:space:]] /etc/clamav/clamd.conf > + value=/var/log/clamav/clamav.log > + [ -z /var/log/clamav/clamav.log ] > + [ /var/log/clamav/clamav.log != LogFile ] > + export LogFile=/var/log/clamav/clamav.log
This bug appears because of the way we get conf parameters values, for LogFile:
grep '^LogFile' /etc/clamav/ clamd.conf clamav/ clamav. log
LogFileMaxSize 0
LogFile /var/log/
LogFileUnlock false
LogFileMaxSize 0
The fix:
diff clamav- daemon. postinst /var/lib/ dpkg/info/ clamav- daemon. postinst [:space: ]]" $CLAMAVCONF | head -n1 | awk '{print $2}'`
175c175
< value=`grep "^$variable[
---
> value=`grep ^$variable $CLAMAVCONF | head -n1 | awk '{print $2}'`
Test: clamd.conf clamd.conf var/log/ clamav/ clamav. log clamav/ clamav. log ] clamav/ clamav. log != LogFile ] /var/log/ clamav/ clamav. log
< + grep ^LogFile /etc/clamav/
< + value=0
< + [ -z 0 ]
< + [ 0 != LogFile ]
< + export LogFile=0
---
> + awk {print $2}
> + grep ^LogFile[[:space:]] /etc/clamav/
> + value=/
> + [ -z /var/log/
> + [ /var/log/
> + export LogFile=