Unisar 1.24.1867 manual Configuration file, System versus User configuration

Page 43

The configuration file

Using

07

BitDefender

 

Chapter 7. The configuration file

The system-wide configuration of BitDefender Antivirus Scanner for Unices is stored inside a file located at /etc/BitDefender-scanner/bdscan.conf on Linux systems and at /usr/local/etc/bitdefender/bdscan.conf on FreeBSD systems. There is another configuration file, located inside the user's home directory, at ~/.BitDefender/bdscan.conf, which is loaded after the system configuration. Therefore, the user can specify settings to override partially or even totally the system settings.

System versus User configuration

In this book we will talk about changing the system-wide configuration file, but remember that you can modify the user's own configuration, with the same effect from his point of view.

The files are standard UNIX-style configuration files, based on pairs key=value, each pair on a single line.

A typical file on a Linux machine could be the following.

#An unpriviledged user can copy this file to the home directory, in

#~/.BitDefender/bdscan.conf and change the settings to suit their

#need. Any setting found in the home directory will overwrite the

#global one.

#

#Check the bdscan.conf(5) man page for more details.

#Where the product is installed

InstallPath = /opt/BitDefender-scanner

#In which directory should files be copied/moved if the action is

#"quarantine"

QuarantinePath = /opt/BitDefender-scanner/var/quarantine

#This file will be used by default for logging if the "--log"

#argument is used

LogName = /opt/BitDefender/var/log/bdscan.log

# By default bdscan scans all the files, but giving the "--ext"

43

Image 43
Contents Users Guide Users Guide As every cat owner knows, nobody owns a cat BitDefender Antivirus Scanner for Unices Table of Contents BitDefender integration UninstallConfiguration file Testing BitDefender Real life usageBest practices UpdatesFrequently Asked Questions Support Product registrationBitDefender Antivirus Scanner for Unices Viii End User Software License Agreement End User Software License Agreement End User Software License Agreement Xii Conventions used in this book PrefaceTypographical conventions Admonitions CommandBook structure Request for Comments Description and features Description and features Overview Why BitDefender?Data Security Division Softwin Description BitDefender Antivirus Scanner for Unices Product featuresKey Features More in the manual Scanning mechanismFeatures Installation Installation System requirements PrerequisitesHardware system requirements Linux requirements Package naming conventionSoftware system requirements Linux conventionFreeBSD convention Installation Test the package for integrity Package installationTest the rpm and deb packages Test the FreeBSD tbz package Test the self-extractable archiveInstall the self-extractable archive Install the packageInstall the rpm package Install the deb packageAdditional parameters Install the FreeBSD package InstallerConfigures the quarantine directory Uninstall using the self-extractable archive UninstallUninstall the rpm package Uninstall the deb packageUninstall a package downloaded locally Uninstall the FreeBSD packageUninstall from the ports collection Using BitDefender Using BitDefender System versus User configuration Configuration fileKey Description More about triggered updateRegular users and quarantine Using07 BitDefenderProduct registration Using BitDefenderScan an executable file Testing BitDefenderEicar online resources Scan an archive Command output will be the followingScan a mailbox Tmp/mail.mbox Virus scanning Real life usageScan a regular file Scan a directory Scan the entire system Actions on archives Scan the archivesScan the mailbox Report Using the log fileDisplay the virus list Get more informationDisplay the product version Virus submissionBitDefender integration Midnight CommanderDesktop integration KDE Konqueror Different installation pathDo not break the last line Action on file in Konqueror KrusaderKrusaders User Actions ROX-FilerPine Information Center PineThis is how the screen should look like What to do with infected emailsExit Status Interval 1,254 BitDefender pipe bdscanpipe EvolutionKMail Filter actions in KMail Server integrationMailScanner installation Qmail-Scanner installationMailScanner Change it to the following form Amavisd-newAmavisd-new installation Using Regular updates UpdatesTriggered update Run the triggered updateEdit the cron table Http proxy Manual updateOrder to extract the updates Trial License License for home or personal use Product registrationCheck the expiration date License for commercial use Best practices Best practices Getting help Getting help Frequently Asked Questions Getting help Support department SupportBitDefender Knowledge Base Softwin GmbH Contact informationWeb addresses AddressBitDefender LLC RomaniaGetting help Manual Pages Manual Pages Description SynopsisOptions Manual Pages Actions Files ExamplesSee also BugsManual Pages Glossary Download Command lineCookie Disk driveHeuristic EventsFalse positive Filename extensionPacked programs Macro virusMail client Non-heuristicStartup items PortReport file ScriptWorm UpdateVirus Virus definition