[Navigation]

Logging in

Before you can access the Premvet software you must first log-in to the system. There are at a minimum three accounts that can be used:

root login
This account is also called The Superuser. The root account on a Unix system has un-limited access - there is nothing the 'superuser' cannot do. For this reason access to root should be restricted only to staff that need to know. You should change the root password on a regular basis (once every 3-4 months), it should also be changed if you suspect someone has access to it when they should not.

You will use the root account to add new users, carry out manual backup's and generally administer the system.

admin login
The admin account is slightly less powerful than root and this is used for the general day-to-day administration of the system and to perform shutdowns.

When you login as admin, (the initial password will have been set to admin) you will be presented with a menu.

The important options are:

Application -> Shutdown the system
Closedown the system correctly.
Application -> X-Menu
Start up the Cross Updating administration menu.
Application -> Sys-Admin
Start up the Unix Administration menu to allow you to add users and generally configure the system. Note: You may not have access to this option initially - if you require it please contact support so they can issue the authorisations.
Application -> X-Session
Start-up the graphical front-end for Unix - you must be on the main console (or X-Terminal) for this to work.
Manager -> General
Manipulate any files (create, remove, change etc.)
Print -> General
Print specific file, cancel jobs etc.
Utilities -> List Users
List all the users that are active on the system.
Utilities -> Disk usage
Show the amount of free space on the system.

Other utilities and applications can be added to this menu, see the main documentation on it in the main Unix documentation:

O.S. Documentation
SCO Shell

vet login
There is an generic login created for initial access to the system, initially there is no password and we recommend this account is passworded and not used for day-to-day work. Note: Do NOT just remove this account it is needed by Premvet 5.

Changing a Unix Password

There are two ways this can be done:

Adding a Unix User

There are many reasons why everyone using the Generic vet login is a bad idea.
Each user should have their own login to the system.

Assuming you are using the basic text screen and not the graphical interface.

Note: To move around the scoadmin character based screen use the arrow keys, tab key and the esc keys. To Exit from scoadmin, select the item at the top left of the menu bar, press ENTER then select EXIT

You will be prompted for:

  • Login: Enter the name you want the user to login as e.g. tom
  • User ID: Just press RETURN to accept the default
  • Comment: Type in the users full name e.g. Tom Melvin
  • Password: Accept the 'Set password now' option
    Press RETURN through the other four options (make a note of the 'Home directory' entry for later).
    The screen will change to the password selection options.
    Select 'Enter a password'
    Give the user a temporary password, you will have to enter it twice.
    Force password change at next login - if you want the user have to change their password when they next login select this item otherwise just press RETURN.
    •

    The account will now be created.

    Note: If the login name you assigned the user is the SAME as their Premvet 5 user name they will NOT be prompted within the vet system for a user I.D.

    You can use the 'Import /etc/passwd' option within Premvet to automatically create these users in Premvet.

    What does the user see when they login?

    One of the first things to do is decide what will happen when the user logs in. You have a choice, and once set you do not need to alter this again unless you need to on specific accounts. You can:

    1. Have the user go straight into the vet system
    2. Start up a 'menu' system to allow other options.
    3. Jump straight to the $ prompt.

    The most common option will be to start the vet system automatically which is the default. You need to decide what to do. You can change every login account you create on a one-to-one basis or change one of the configuration files to affect all logins you create.

    Whenever a user logs in there is a file in their home directory called .profile that sets up and runs the initial programs. When you created the first user there was an option 'Home Directory', which will have been either /usr or /u - this will be referred to as $HOME.

    type the following command:

    tail $HOME/user-name/.profile
    e.g. tail /u/tom/.profile

    The last line shown on the screen is what happens:
    exec vet Start up the vet system automatically
    exec scoshStart up menu system automatically
    Anything ElseWill give the $ prompt.

    Try the different options to see what you prefer. Once you are happy and have decided on the 'practice configuration' you can alter the file /usr/lib/mkuser/sh/profile to make this the default setting for all future users you create.

    Create as many individual logins as you want.

    There are other options in scoadmin - account manager for retiring, deleting, changing passwords etc. Have a wander through them they are fairly self-explanatory.

  • Use <TAB> to jump to the list of users
  • Select the one you want
  • Use <TAB> to jump back to the options, select Users
  • Select the required option

    • Why not use the Generic Login

    There are a few reasons why using individual logins is a good idea:

  • Improves security
  • Gives better control
  • Reduces system overhead
  • Makes better use of E-mail, Calendars, home directories
  • Allows customisation of user environments.
    •

    Lets look at these in a bit more detail:

    Performance

    The system allocates internal tables and other resources so you as a user do not need to worry about running short. If everyone is logged in as the same user then the system has to allocate a fair amount of resources to support them, this leads to large tables which take longer to search and maintain.

    Administration

    If you ever had to use find out who was on the system or who was using a terminal and used the who or Admin -> Utils -> List Users, - you would have had difficulty as all would be showing 'vet'. With individual logins it is fairly easy: 
    9:14pm up 1 day, 10:36, 36 mins, 7 users, load average: 0.04, 0.00, 0.00
User   Tty    Login@   Idle   JCPU  PCPU What
root   tty01  10:43am  00:38  00:00   -    w 
tom    ttyp5  10:56am  00:48  00:00   -    xc 
andy   ttyp7   9:13pm  1      00:01 00:00 run14 v6menu 
lee    tty001 10:43am  15     33:04 00:00 run14 v6menu
fiona  tty003 10:43am  34:30  00:00 00:00 run14 v6menu
root   tty04  11:15pm  21:59  28:27 14:23 netscape
root   ttyp0  11:15pm 814:42  00:00 00:00 -

    You will also find it a lot easier to use the inter-terminal communication program e.g. talk and write as you know where the user is.

    Security & Accounting

    If you are wanting to track down when someone logged into system, using the generic vet you can't. However, with individual logins there are some commands, mainly 'last' that show you just than e.g. 
    User    Line Device    PID   Login  time  Elapsed Time Comments
tom     p0   ttyp0    27306  Mon Mar 16 22:21 00:01     logged in
andrew  ETNk tty1A06  22319  Mon Mar 16 21:10 00:35 
fax_inc ETNh tty1A03  16880  Mon Mar 16 18:52 00:00 
aileen  p0   ttyp0    15318  Mon Mar 16 18:05 03:03     ??
lee     p1   ttyp1    14863  Mon Mar 16 18:00 04:22     logged in
bppp    ETNk tty1A06  10652  Mon Mar 16 17:08 00:05

    This can be used to show who and when they logged on. Additionally, logins over night or at times where that member of staff is not expected can be investigated.

    Home Directories

    All individual logins are given their own area of the hard disk. This is basically private and users can keep track of their personal files, web home pages etc. This is also more important when the user has a networked PC. This area can be used to store all the important files that need backing up overnight.

    Other application

    The most noticeable one is e-mail - we are using e-mail more and more in the form of mailing lists, cross updating errors, support etc. With a generic login, everyone sees everyone else's mail. In due course e-mail will be replacing the built in Premvet message system. Individual logins allow the mail to be directed at the correct user and remain private. Other built in applications include, the SCO shell, calendar.

    Customisation

    With the Vet System, e-mail, SCO shell, calendar etc. all these application have the ability to be customised by the user. Generic vet login force one set of parameters on all users.

    Drawbacks

    There is one drawback to individual logins, someone has to create and maintain them. New member of staff will need a login account created. When someone leaves - the account has to be removed. However, these procedure are fairly easy.

    Top Classic New-Style Chapters Sections Index Search