The Nvdd.conf.lock File; User_Rep Files - Neoware e140 - Thin Client User Manual

NVDD Temporary Files

The nvdd.conf.LOCK File

USER_REP Files

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