Download System Administration

6.3 Multiuser Setup for VNMR
lock and is present by mistake, the lock file belongs to root (which runs Expproc or
Acqproc), and unlock refuses to remove the lock file. However, the user can still
remove that lock file using the rm command8.
Files on Other Disks or Disk Slices
Systems with two or more disks usually have extra disk slices for data storage (the name
/data is suggested). On systems with a small first disk and a big second disk,
/export/home should be installed on the second disk, to allow for more flexibility with
big experiments. The remainder of the first disk can then be mounted as /data.
Home directories can also be located in directories other than /export/home. Certain
parts of VNMR (or customized macros) may assume that all home directories are in
/export/home; therefore, a file in /data would not be found. This problem is
bypassed by creating a symbolic link /export/home/xx pointing to /data/xx, such
that for the software the file still seems to be in /export/home. Use the Solaris
admintool to create new users. This way, it is assured that the password file
/etc/passwd contains the proper information about the location of the home directory.
6.3 Multiuser Setup for VNMR
The directory /export/home/vnmr contains all the files that are (and must be) globally
available. Because /export/home might contain various VNMR directories (e.g.,
vnmr53b, vnmr61a), to simplify access to the VNMR software directory, a symbolic
link /vnmr is established, pointing to the currently active software directory. Usually,
when addressing /vnmr, we actually don’t mean the symbolic link, but the directory that
link points to.
All users can read the data within /vnmr and also execute any macros, pulse sequences,
shell scripts, etc. within this directory. In the default setup, only the NMR system
administrator vnmr1 can make modifications to files in /vnmr.
Every user has and can use their own (local) pulse sequences, macros, menus, parameter
sets, shell scripts, etc. Each user can also modify files from /vnmr by creating a local copy
and modifying that file (which would then be located in his own psglib, maclib,
menulib, seqlib, parlib—all in the user’s vnmrsys directory or within a local bin
file for shell scripts).
If the user calls a macro that exists under the same name both in his local maclib and in
the global maclib (/vnmr/maclib), the system executes the local macro, i.e., the local
directories are looked up first. This is useful feature, but it can potentially create problems
because the system always uses a local pulse sequence, while the global file (with the same
name) may have been improved or upgraded.
The general idea is to keep the system software clean and to modify it as little as possible.
If vnmr1 wants to make changes available to all users, he or she may decide to put
something into /vnmr on a case-to-case basis (make sure you keep a log of what
modifications are done in /vnmr—this will be helpful when upgrading to the next VNMR
release).
For macros, an additional directory can be searched automatically if this directory is
specified in a (global) VNMR parameter maclibpath. This additional directory would
8.
The ability to remove a plain text file is not controlled by the permissions and the ownership of the
file itself, but rather by the permissions of the directory in which the file resides.
01-999166-00 C0503
System Administration
117