Chapter 6. NOD32 system update and maintenance
base directory, i.e. directory where the NOD32 anti-virus scanner will load the modules from).
One can choose an arbitrary directory for this purpose, however, this must contain nod32.000
module. There is no requirement given on the version of the module. In case the module is not
located in the directory chosen, error 105 will occur. It is recommended to set NOD32 base direc-
tory as ’/var/lib/nod32’ as this is exactly the default directory where the modules are loaded
by NOD32LMS anti-virus scanner from. In case the NOD32 base directory is not chosen by the
user it is defined by default as the current working directory.
In case the ’update.ver’ file located in the mirror directory is not signed by valid digital signa-
ture, error 107 will appear. One can force nod32upd to not check the digital signature of the file
by choosing switch ’--no_signature’.
Please refer to the manual pages nod32upd to get detailed information on the command line
options.
6.2. Subordinate mirrors creation
After download of NOD32 modules the nod32umc utility will create in the mirror directory the
’update.ver’ file containing the information about the modules currently stored in the newly
created mirror. The newly created mirror is a fully functional mirror of NOD32 modules stor-
age and can be used in the process of additional mirrors creation. This hierarchy allows the
user to update all the modules in all the subsequently created mirrors without using, and thus
overloading, one and the same mirror server (see figure 6-1 for details).
Figure 6-1. The scheme of subordinate NOD32 mirrors creation. With the presented
hierarchy it is not necessary to perform update process of the mirror C1 by tasking the
mirror A which preserves the appropriate server from the overload.
MIRROR A
MIRROR B1 MIRROR B2
MIRROR C1 MIRROR C2
37
To Next Page
Loading...
Need help?
General
