Hallo,
#1 It seems that You mix two different things together - in the fact, avastcmd has nothing to do with avastd. avastd is a central scanning service, which communicates with its thin clients, such as avastlite. avastcmd is a standalone scanner which doesn't depend on avastd (only uses the same in-memory shared virus database as avastd, but this sharing is fully transparent)
#2 scanning more directories is simple - use more arguments, example: avastcmd /var /opt
#3 actions can't be performed with the avastd directly - it's protocol doesn't allow it, and such actions are hard to "hardwire" in a generic manner - for example, infected mail should be treated differently than infected executable file in user's home. these actions are up to its thin clients.
#4 yes, avastcmd (a a standalone on-demand cmdline probe) doesn't contain this - it's intended for use in on-demand scripts and simple shell constructs like
avastcmd /home/vxer/my_viruses | grep "\[infected by:" | while read a b; do WHAT YOU WANT WITH $a; done
have faaar better flexibility than any hard-wired action, IMHO.
regards,
PC