This chapter provides information about:
Checking the installed version string to verify installation
Configuring your system for general use, either with the SysMan Configuration Checklist or from the command line
Enabling realtime preemption after the installation
Enabling unattended reboots on multiprocessor systems
The goal of this chapter is to provide the information necessary for you to perform the user actions shown in Table 7-1.
| By reading this chapter, you will ... |
| Check the installed version string to verify installation. |
| Invoke the SysMan applications using either the graphical or text-based interface to configure your system for general use. |
| Know the disposition of files left over after the installation. |
| Enable realtime preemption after the installation. |
| Enable unattended reboots on multiprocessor systems. |
If you need more information about setting up the system for general use, read the relevant manuals in the documentation set:
The Network Administration guide provides information about setting up and administering a network.
The System Administration guide provides information about system administration tasks such as configuring printers, adding user accounts, backing up and restoring files, shutting down the system, and so on.
The Software License Management guide provides information about loading and registering license PAKs.
Chapter 8 describes how to view the online documentation set and copy the documentation files from CD-ROM to your system.
To verify that you have installed all of the correct elements in this version
of the operating system software kit, check the operating system revision level in
the
/etc/motd
file.
The correct version string is
DIGITAL
UNIX V4.0F.
If your system has graphics capabilities, system setup is done from the
SysMan Configuration Checklist.
This checklist provides access to the SysMan
applications that are available to set up your system for general use.
There are three
ways to invoke the checklist:
The first time you log in as
root
after a system
installation or the first time you log in to a factory installed software (FIS) system
with graphics capabilities, the
SysMan Configuration Checklist
displays automatically.
To open the
SysMan Configuration Checklist
from
the UNIX command line, as superuser or root, enter the following command:
#/usr/sbin/checklist
To invoke the
SysMan Configuration Checklist
from
the Common Desktop Environment (CDE) front panel:
Click on the
Application Manager
icon on the CDE
front panel.
Double click on the
System_Admin
application group
icon.
Double click on the
SysMan Configuration Checklist
application icon.
For your system to be fully productive and
communicative with other systems and users, you may want to add user accounts, and
configure the network, mail, and printers.
In addition, when you buy a product, you
receive a license for its use.
The license is described by the license Product Authorization
Key (PAK) you received.
To be officially authorized to use the operating system, you
must register the license information on the PAK by using the
License Manager
application.
The
SysMan Configuration Checklist
provides access to a number
of SysMan applications including but not limited to the applications shown
in
Table 7-2.
Table 7-2
also lists the reference pages associated with the SysMan applications.
| SysMan Application | Reference Page |
| Network Configuration Application |
netconfig(8) |
| BIND Configuration Application |
bindconfig(8) |
| NIS - Network Information Service |
nissetup(8) |
| NFS Configuration Application |
nfsconfig(8) |
| License Manager |
dxlicenses(8) |
| Account Manager |
dxaccounts(8) |
| Mail Configuration Application |
mailconfig(8) |
| Disk Configuration Application |
diskconfig(8) |
| LAT - Local Area Transport |
latsetup(8) |
| UUCP - UNIX-to-UNIX Copy System |
uucp(1) |
| NTP - Network Time Protocol |
ntpupdate(8) |
| Printer Configuration Application |
printconfig(8) |
| Security (BSD/2) |
secsetup(8) |
| Security Auditing |
audit_setup(8) |
| Prestoserver I/O Acceleration |
presto(8) |
| Update Administration Utility |
updadmin(8) |
| Graphical UI Selection Utility |
|
To invoke a SysMan application, double click on the icon that appears to the left of the application name. After you invoke and exit an application, a check mark appears in the box to the left of the icon. The date and time you last accessed an application is shown under the application name.
You can view an online overview of the
SysMan Configuration Checklist
applications by clicking on the
Help
button located
at the lower right hand corner of the
SysMan Configuration Checklist
main window.
The applications on the
SysMan Configuration
Checklist
appear in the approximate order in which they should be run.
For
instance, if you plan to connect or add the system to a network, the first task you
should perform is to set up the network by using the
Network Configuration
Application
followed by the
BIND Configuration Application,
NIS - Network Information Service, and the
NFS Configuration Application.
If you do not want to set up networking, the first task you should perform
is to load and register your Product Authorization Keys (PAKs) using the
License Manager.
An application that is dimmed is not available from the checklist because it is not installed on the system.
Online help is available for each SysMan application by clicking on
the
Help
button in the application.
The online help describes how
to use the application, the entries to make in the text entry fields, and reference
material.
If your system does not have graphics capabilities, you can access a set of menu-driven, text-based system setup scripts to set up your system for general use.
You can access this setup menu from the command line as the user
root
by entering the following commands:
#su -password:#/usr/sbin/setup
A menu similar to the following is displayed:
Use this menu to set up your system and network. When you
select an item, you will be asked a series of questions.
For more information about the items on the menu and the
questions you must answer, see the System Administration
and Network Administration guides.
1) Network Configuration Application
2) BIND Configuration Application
3) NIS - Network Information Service
4) NFS Configuration Application
5) License Manager
6) Mail Configuration Application
7) LAT - Local Area Transport
8) UUCP - UNIX-to-UNIX Copy System
9) NTP - Network Time Protocol
10) Printer Configuration Application
11) Security (BSD/C2)
12) Security Auditing
13) Prestoserve I/O Acceleration
14) Update Administration Utility
15) Graphical UI Selection Facility
16) Exit
Enter the menu item number that you want:
Availability of the setup scripts on this menu depends on the software subsets that were installed. In the previous sample menu, all mandatory and optional software subsets were installed, so all setup scripts are available. If a setup script does not have an option number next to it, the setup script is not available for use.
Each of the setup scripts is a series of interactive prompts during which questions are displayed on the screen and you respond accordingly. Most questions provide you with default responses and in most cases, you can choose the defaults. Any default parameters that you accept can always be changed at a later time.
The setup scripts appear on the menu in the order in which they should be run.
For instance, if you want to set up the system to run in a networked environment,
the first task you should perform is to set up networking information by using the
Network Configuration Application
followed by the
BIND Configuration
Application,
NIS - Network Information Service, and the
NFS Configuration Application.
If you do not want to set up your system
to run in a networked environment, the first task you should perform is to load and
register your Product Authorization Keys (PAKs) using the
License Manager.
You should read the relevant sections of the documentation set before running a setup program or choosing an option from the Setup menu. The documentation lists the prerequisites to running a specific setup program.
The Network Administration guide provides information about setting up and administering a network.
The System Administration guide provides information about system administration tasks such as configuring printers, adding user accounts, backing up and restoring files, shutting down the system, and so on.
The Software License Management guide provides information about loading and registering license PAKs.
Chapter 8 describes how to view the online documentation set.
Several files are left over after the installation process completes. The following files are of particular interest:
The installation procedure leaves the
init
file
in the
/tmp
directory.
This is an unnecessary file that you can
delete.
Many files with the prefixes
.new..
and
.proto..
are left on the system.
The update installation process documented
in
Chapter 2
requires these
.new..
and
.proto..
files to retain customized system files.
Caution
Do not remove these
.new..and.proto..files!
A list of the log files created during the installation is displayed on the screen (or in the console log if you have a workstation) after you log in for the first time. The display is similar to the following:
DIGITAL UNIX V4.0F (Rev. nnn); Fri DEc 17 15:54:51 EST 1999 DIGITAL UNIX V4.0F Worksystem Software (Rev. nnn) The installation software has successfully installed your system. There are log files that contain a record of your installation. These are: /var/adm/smlogs/install.cdf - configuration description file /var/adm/smlogs/install.log - general log file /var/adm/smlogs/install.FS.log - file system creation logs /var/adm/smlogs/setld.log - log for the setld(8) utility /var/adm/smlogs/fverify.log - verification log file
The previous message is also recorded in the
/etc/motd
file
for your future reference.
The
/etc/motd
file contains the
message of the day
that is displayed each time a user logs in.
The installation
log files are located in the
/var/adm/smlogs
directory and include
the choices you made during the installation such as the disks and partitions you
chose, the software subsets you installed, and so on.
The operating system kernel provides options to enhance the performance of realtime applications conforming to POSIX® 1003.1b-1993 (formerly 1003.4 Draft 14). The realtime kernel makes it possible for the operating system to guarantee that an application has access to resources in a timely and predictable manner.
The realtime kernel that supports kernel preemption was previously installed as an option during base system installation. Now, the POSIX 1003.lb portions are included in the kernel automatically and a separate kernel is not needed. Preemption capabilities are disabled by default, but can be selected and enabled when the kernel is configured and built.
There are two methods to obtain additional realtime capabilities:
Use a text editor of your choice to
edit the
/etc/sysconfigtab
file and set the
rt_preempt_opt
parameter in the
generic
section equal to 1 as shown
in the following example:
generic:
rt_preempt_opt=1
After setting this parameter,
you must reboot your system.
When the
rt_preempt_opt
parameter
is set, the system chooses the correct lockmode to support realtime preemption.
On
a single processor system, the lockmode is set to
1.
On a multiprocessor
system, the lockmode is set to
3.
You can also use the
setld
command to enable realtime preemption as shown in the following example:
Use
the
setld
command as follows to configure the
OSFBIN440
subset:
#setld -c OSFBIN440 RT_ON
Refer to the
setld(8)
reference page for additinional information.
After this operation, the kernel configuration file contains the entry
options rt_preempt_opt
that causes preemption to be on by default (in the
appropriate lockmode).
Run
doconfig
without
any options to generate a new kernel configuration file.
If necessary, refer to the
doconfig(8)
reference
page.
Copy the new kernel file created in
/usr
to the
root
directory as the file
/vmunix.
Reboot your system.
An unattended reboot feature is available for multiprocessor platforms to reduce system down time because of a processor failure.
To enable unattended reboot functionality, halt the system and set the following console parameters:
>>>set boot_osflags a>>>set boot_reset off>>>set auto_action restart
When processor failures are detected on a multiprocessor platform, the system marks
the faulting processor as failed, and the entire system is rebooted without any operator
intervention.
The faulting processor will not be restarted when the reboot occurs.
To restart the faulting processor, corrective action must be taken.
The system will
not try to restart the failed processor until the power has been recycled on the system
or the console
init
command is issued at the console prompt (
>>>
).