Daylight Summer School 2001, June 5-7, Santa Fe, NM
Daylight Worksheet - Security and Customization of Databases
Daylight databases are configurable in several ways. Configuration
options are stored as fields in the header file for the database
(the .THOR file). The header file can be edited directly, as it
is a simple text file. However, the approved and more reliable
method is to use a Thor-manager client (sthorman, thorchange, etc.).
- Auxilliary Databases - All databases have at least one
auxilliary database, a datatypes database. Other possible
auxilliary databases are indirect and monomer. The auxilliary
databases can be set at database creation, and can be modified
Try changing the datatypes database of a regular database.
This may make the database dysfunctional since database will
no longer be defined. Change it back to correct the situation.
- Database Passwords - Databases each have three passwords:
read, write, and executive. Set all three passwords for a
database and access the database to test that the passwords work.
Then set all passwords to null "".
- Read-only - Databases can be set to read-only. Set a
database read-only using
thorchange -SETACCESS READONLY <DB>
and verify its state by attempting to open writeable with
xvthor. Then revert to
- Caching - Databases can be configured for caching in several ways
to improve their performance (speed). Caching forces the Thorserver
to hold some or all of a database in memory for fast access, and
supplements the operating system's normal file caching. Modify a
database's cache configuration with a command like
thorchange -CACHE_WHEN ALWAYS -CACHE_LEVEL WRITETHRU<DB>. Inspect the .THOR header file to see how this is stored.
Return the database to its original state with another command.
Daylight Chemical Information Systems Inc.