After this starting my machine takes really long because starting clamav-daemon takes much time.
Found no hint on internet. Tried some things after looking into the source.

The problem is that daemonizing happens after reading the database, so starting via start-stop-daemon
blocks the init script.

Tried no to use to fork start-stop-daemon instead and this gives me the old start behaviour back.

I changed in /etc/init.d/clamav-daemon from:

    start-stop-daemon --start --oknodo -c $User --exec $DAEMON --pidfile $THEPIDFILE --quiet -- -c $CLAMAVCONF --pid=$THEPIDFILE

to this:

    start-stop-daemon --start --oknodo -c $User --background --exec $DAEMON --pidfile $THEPIDFILE --quiet -- --foreground -c $CLAMAVCONF --pid=$THEPIDFILE

With this change start-stop-daemon forks and this fork starts clamd in forground. clamd then can load the database in forked proces and
does not block the init script anymore.

Is this a bug report worth?
Which bug tracker?

With kind regards
Stefan