Editando o clamd.conf como abaixo, o problema resolve
# Log additional information about the infected file, such as its
# size and hash, together with the virus name.
#ExtendedDetectionInfo yes
# This option allows you to save a process identifier of the listening
# daemon (main thread).
# Default: disabled
PidFile /var/run/clamd.pid
# Optional path to the global temporary directory.
# Default: system specific (usually /tmp or /var/tmp).
TemporaryDirectory /var/tmp
# Path to the database directory.
# Default: hardcoded (depends on installation options)
DatabaseDirectory /usr/local/share/clamav
# Only load the official signatures published by the ClamAV project.
# Default: no
#OfficialDatabaseOnly no
# The daemon can work in local mode, network mode or both.
# Due to security reasons we recommend the local mode.
# Path to a local socket file the daemon will listen on.
# Default: disabled (must be specified by a user)
LocalSocket /tmp/clamd.socket
Agora, se eu digitar 'clamd & amp;' está mostrando
[3] 12859
Então 'serviço do sudo clamav-daemon start' mostra
[3] Feito clamd
Então 'clamdscan -v' mostra
/ usr / local / etc: OK
----------- RESUMO DA VERIFICAÇÃO ----------- Arquivos infectados: 0 Tempo: 0,017 seg (0 m 0 s)
Então 'clamdscan -V' mostra
ClamAV 0.99.1 / 21490 / Ter 12 de abril 08:04:23 2016