
1. When you execute bdc --update, you might see in the installation
directory two .dll files, brought by update. This is a behaviour
caused by the common platform of BitDefender scanning engines with
the Windows version. However, BitDefender will provide a fix for this
in a future release.
Also, this issue will not harm at all the overall functionality of
BitDefender for Linux Console.

2. Rarely, bdc may crash while scanning a file. If such a crash
occurs, the main reason for this is the lack of some .cvd files from
the plugins directory. To prevent future crashes caused by this reason,
run bdc --update and restart the scanning process.
If you want to get details, you may repeat the scanning process (before
updating) using the strace program, which is included by default in
most Linux distros. If the crash repeats, attach the last 20 lines of
strace output in a mail sent to our support team.
support@bitdefender.com

3. In some cases bdc may hang while scanning special files such as pipes
or UNIX sockets. Therefore the scanning of these files must be avoided
as much as possible. This behaviour will be fixed in the next release.

4. If, for some reason, you will have a corrupted bdc.ini file, bdc will
fail the update with the following message:
No update available
To fix this issue, edit bdc.ini to insert/correct the UpdateHttpLocation
directive as follows:
UpdateHttpLocation = http://upgrade.bitdefender.com/update7

If you are aware of, or discover any other problem regarding bdc
behaviour, please email our support team.
