There are some messages that may appear when starting up the vet system, this chapter explains what they are. Note: This applies only to the vet system - Operating System messages are covered in the OSR 5 manual.
Lock file present unable to remove device entry Lock file present unable to create device entry
If either of these messages occur you should check that there are no users logging on and then remove the file:
$VETSYS/device.LCK(Where $VETSYS is the data directory for premvet 5 e.g. /u/vetdata )
Sorry unable to mount filesystem - check disk is present Sorry unable to un-mount Jaz disk - will need to handle manually Sorry cannot find a vet system in xxxxx Sorry - jaz is mounted - some-one may be using it
Sorry I cannot work out where Premvet files are located. xxxxxxxxx - is either missing or invalid.
Check that the data directory specified either on the
command line with the -d
option or the default entry
in /etc/default/vet3000 is correct.
Sorry I cannot work out where Premvet programs are located. xxxxxx - is either missing or invalid.
Check that the program directory specified either on the
command line with the -s
option or the default entry
in /etc/default/vet3000 is correct.
xxxxxxx exists indicating a backup is in progress at present. You are not allowed access to the system. Please try later.
The system is currently in maintenance mode." You are not allowed access to the system. Please try later.
It is NOT recommended that the Vet System be run by root. If you must, use vet -r to start up, ensure that you check the file permissions in /u/vetdata when finished.
echo "User licence exceeded"
vet -V.
Please type 'exit' to quit current sub-shell first
| Top | Classic | New-Style | Chapters | Sections | Index | Search |