This section of the manual will explain what configuration files are used and what they can contain:

/etc/default/vet3000

This is the main config file, it is a standard text file and contains:

# Main Premvet script to set startup variables

VETSYS=/v/vetdata       # Where are the main data files located
SOURCE=/u/source        # Where the Programs live

# VETTEST=/dev/tty0100     # Location of vet test machine
# WebServer=""          # Where is the Web Server

VETSYS=

The location of the main premvet 5 data files

SOURCE=

Where the programs are, if left blank this will default to /u/source

VETTEST=

Optional - If there is an IDEXX machine connected - What port is it connected to.

WebServer=

Optional - By default the help sub-system will use the Web Server on the Unix host the software is installed on. You can specify another machine using the WebServer option. If you are using the basic host version or an early version of OSR5 that does not have a Web Server set this option to null e.g. WebServer="", if you are using an enterprise version of OSR5 but have not yet configured it use WebServer="localhost".

M_Style=2

Optional - Switches the system over to use new style menus.

Mapchan=No

Optional - Stops Premvet resetting the character codeset on startup if you are configured for the euro.

This is a program that is run every time the system is brought into multiuser mode. Its purpose is to:

• Mount the RAM disk if configured
• Delete any lock files, e.g. Vat book, Cross updating and purchase locks
• Delete the files that record the current users.
• Delete any old /tmp/prn files
• Start the VetTest Daemon (if Idexx link installed)

This file is used to set any global variables for use within the Vet Software. It is 'sourced' from /etc/profile so will always be loaded. Currently, it contains one line:

O_TTY=`tty` ; export O_TTY

Multiple Copies of Premvet 5

• You can create a shell scripts that called the main vet program file and using the command line options tell the system to look else where for the data files e.g. vet -d /u/play. Command line options are covered in the section Command Line Options
• or, you can make a copy of this startup program, then create a file in /etc/default of the same name. This configuration file will be read AFTER vet3000 so you could alter VETSYS to point to another copy of the data.

  e.g. You have a play copy of the files for training purposes, you would make a link between /usr/local/bin/vet and /usr/local/bin/play e.g.

   ln -s /usr/local/bin/vet /usr/local/bin/play

  then create the file /etc/default/play with the line VETSYS=/u/where-ever.

If you are using the system with two live sets of data BOTH with a generic login (e.g. vet and play) - you may need to use the command switch vet -E to ensure that users using the 2nd generic account are asked for a vet system password.