25
module (nod32.005) and ThreatSense.NET support module (nod32.006) in the directory:
/var/lib/nod32
resp. in RedHat Ready and Novell (SuSE) Ready variation of the product the target directory is as follows:
/var/opt/eset/nod32/lib
Note that the above directory is exactly the NOD32 base directory where main NOD32 daemon loads NOD32
modules from.
6.2. Automatic update of the virus denitions database
To provide the highest security for the user, the NOD32 team collects the virus denitions continuously from all
over the world. The new patterns can appear within the database in very short intervals. It is therefore useful, and also
recommended, to trigger an update attempt on a regular basis.
Threre are two ways to provide periodic update of the system. First, the main NOD32 daemon can provide the update
once ‚av_update_period‘ parameter dened in [update] section of the main NOD32 conguration le. Second, the
update can be triggeret externally by using script:
/usr/sbin/nod32_update
Note that the Linux RedHat Ready and Linux Novell (SuSE) Ready products locates the script in directory
/opt/eset/nod32/sbin/nod32_update
In order to trigger update script in one hour intervals, congure periodic scheduler (cron) in Linux OS and BSD OS
by entering the following line
0 * * * * /usr/sbin/nod32_update
into its conguration le (crontab). To add the above line into the crontab use command line statement
crontab -e
to invoke the editor set up for the current system environment (dened by EDITOR environment variable).
Similar command is valid for Linux RedHat Ready and Linux Novell (SuSE) Ready product
0 * * * * /opt/eset/nod32/sbin/nod32_update
chapter 6 / NOD32 system update and maintenance
To Next Page
Loading...
Need help?
General
