NVDD Temporary Files348 The nvdd.conf.LOCK FileIf the NVDD server crashes, due to a power failure for example, thetemporary file current.nvdd.conf will still remain in the directoryspecified by client_files_dir. The next time nvdd is launched itwill copy any files prefixed with current. into a subdirectory of theclient_files_dir called restoredfiles, and add a timestamp tothe end of each filename. This makes it possible for an administratorto recover configuration files that include changes that have not yetbeen applied.The nvdd.conf.LOCK FileIn order to prevent conflicts, a configuration file can only be openedby one nvdd process at a time. When nvdd is launched it creates afile with the same name as the configuration file but appended by.LOCK. This file will be placed in the same directory as the configu-ration file.When nvdd is launched again, it checks that there is no .LOCK filethat corresponds to the configuration file it is attempting to use. Ifthere is a .LOCK file then nvdd will refuse to launch.If the NVDD server crashes, due to a power failure for example, the.LOCK file will still remain. You must manually delete or rename the.LOCK file in order to be able to launch nvdd.CAUTION: Before you actually delete the .LOCK file and launchnvdd with the related configuration file, ensure that no other nvddprocess is actually using the locked configuration file, otherwise youmay corrupt your configuration file as well as your server execution.USER_REP FilesClient names set by the NVD protocol are stored in the configurationfile. In certain conditions these names can be changed from the cli-ent side. In order to preserve the integrity of the configuration fileand to allow two clients to change their names at the same time, thedata relating to changed client names are temporarily stored in a file
