Home » HP Manuals » Desktops » HP Visualize J210XC » Manual Viewer

HP Visualize J210XC IRIX to HP-UX Migration Guide - Page 82

Configuring the Name Service Switch

View all HP Visualize J210XC manuals

Add to My Manuals
Save this manual to your list of manuals

Page 82 highlights

Domain Name Service Configuring the Name Service Switch The Name Service Switch determines where your system will look for the information that is traditionally stored in the following files: /etc/hosts /etc/protocols /etc/services /etc/networks /etc/netgroup /etc/rpc For all types of information except host information, you can configure your system to use NIS, the local /etc file, or both, in any order. For host information, you can configure your system to use BIND (DNS), NIS, the /etc/hosts file, or any combination of the three, in any order. The default Name Service Switch configuration is adequate for most installations, so you probably do not have to change it. NOTE: Configuring the Name Service Switch is a separate task from configuring the name services themselves. You must also configure the name services before you can use them. The Name Service Switch just determines which name services are queried and in what order. You can use SAM to configure the Name Service Switch. The following are some suggestions for customizing your Name Service Switch configuration: • If you want your system to consult the local /etc/netgroup file when it fails to find a netgroup in the NIS netgroup database, create or modify the netgroup line in the /etc/nsswitch.conf file as follows: netgroup: nis [NOTFOUND=continue] files • If you want your system to consult BIND (DNS) when it fails to find a host name in NIS, create or modify the hosts line in the /etc/nsswitch.conf file as follows: hosts: nis [NOTFOUND=continue] dns files • With this configuration, if NIS does not contain the requested information, and BIND is not configured, the /etc/hosts file is consulted. • If you want your system to consult NIS if it fails to find a host name in BIND or if the BIND name servers are not responding, create or modify the hosts line in the /etc/nsswitch.conf file as follows: hosts: dns [NOTFOUND=continue TRYAGAIN=continue] nis files With this configuration, if BIND does not return the requested information, and NIS is not running, the /etc/hosts file is consulted. HP recommends that you maintain at least a minimal /etc/hosts file that includes important addresses like gateways, diskless boot servers and root servers, and your host's own IP address. HP also recommends that you include the word "files" in the hosts line to help ensure a successful system boot using the /etc/hosts file when BIND and NIS are not available. CAUTION: Changing the default configuration can complicate troubleshooting. The default configuration is designed to preserve the authority of the name service you are using. It switches from BIND to NIS only if BIND is not enabled. It switches from NIS to the local /etc file only if NIS is not enabled. It is very difficult to diagnose problems when multiple name servers are configured and enabled for use. 77

Section	Page
IRIX to HP-UX Migration Guide	1
Prepared by the Technical Computing Division	1
Hewlett-Packard Company	1
1. INTRODUCTION 1	6
1. Introduction	6
Purpose and Scope	6
System Administration	6
HP-UX and IRIX	6
2. System Startup and Shutdown	8
IRIX	8
Normal Boot	8
Single-user Boot	8
System Shutdown	9
HP-UX	9
Normal Boot	9
pdc	9
isl	9
hpux	9
Single-user Boot	10
	10
	10
	10
	10
	10
Select from menu: b p0 isl	10
ISL>hpux –is	10
Startup	11
/sbin/rc	11
Execution scripts	11
Configuration Variable Scripts	12
Link Files	12
Run Levels and /sbin/rc	13
Example	13
System Shutdown	13
Summary	14
3. User Login	15
IRIX	15
Login	15
User Attributes	15
Adding Users	15
Logout	15
HP-UX	15
User Attributes	16
Logout	16
Summary	16
4. Devices	17
IRIX	17
Introduction	17
Checking Devices	17
Device Files Directory	17
Adding Devices	18
HP-UX	18
Device Files Introduction	18
Device File Naming Conventions	19
Disks	19
Examples	19
LVM Devices	20
Physical volumes	20
Volume groups	20
Logical volumes	20
9-Track Reel Tapes and DDS/DATs	21
Examples	21
Terminals, Modems, and Printers	21
Examples	22
Major and Minor Numbers	22
Creating Device Files	23
The mksf command	24
Examples	24
The insf command	24
Examples	25
mksf v. insf	25
Modifying the Kernel in Order to Add a Device	26
Rebuilding the Kernel Manually	26
Using SAM to Rebuild the Kernel	26
Summary	27
	27
	27
IRIX File System Device Files	27
HP-UX File System Device Files	27
5. Disks and File Systems	29
Directory Structures	29
Directory	29
Directory	30
IRIX File System	30
Logical Volume Manager	30
Basic facts	30
Journaled File Systems	31
IRIX Disk Logical Volume Creation	31
IRIX Logical Volume Increase	31
HP-UX	31
Logical Volume Manager	31
Basic Facts	32
Managing Logical Volumes Using SAM	32
Managing Logical Volumes Using HP-UX Commands	32
Physical Volume Management Tasks	32
Changing the characteristics of a physical volume in a volume group	32
Volume Group Tasks	33
Task	33
Creating a Logical Volume Using HP-UX Commands	33
File Systems	34
An Introduction to VxFS	34
Creating a File System	34
Mounting file systems	35
Mounting File Systems Automatically at Bootup	36
Extending the Size of a File System Within a Logical Volume	36
Disks and File Systems: IRIX vs. HP-UX	36
6. Managing Processes	37
IRIX	37
The ps Command	37
Priorities and Nice Values	37
Signals	37
	37
	37
	37
STOP	37
Cron	38
HP-UX	38
ps, nice, and renice	38
Signals	39
Starting and Stopping Subsystems	40
Process Management Commands	41
top	41
sar	41
vmstat	41
iostat	41
Cron	41
Summary	41
7. Backups	42
IRIX	42
HP-UX	42
fbackup	42
Examples	43
frecover	43
Examples	44
HP-UX and Cartridge Tapes: tcio	44
Examples	44
Creating a Bootable System Backup	44
Interoperability Issues	45
Standard UNIX Utilities	45
Backup Utilities Comparison	45
Summary	45
8. Printers	47
The IRIX Print Spooler	47
Managing the lp System	47
Adding a Parallel or Serial Printer	47
Restarting the lpsched Daemon	48
After you have defined the appropriate parallel and/or serial printers, the lpsched daemon must be restarted. To restart the lpsched daemon:	48
Adding a Network Print Server	48
Removing a Printer	48
Changing the Default Printer	49
Managing Printing on Print Server Systems	49
Checking the Print Server Status	49
Canceling Print Server Requests	49
HP-UX Print Spooler	49
lp Spooler Tasks	49
Specifying the Printer Model File to the lp Spooler	49
Adding a Local Printer to the lp Spooler	50
Adding a Remote Printer to the lp Spooler	50
Adding a Network-Based Printer	51
Creating a Printer Class	51
Removing a Printer from the lp Spooler	52
Removing a Printer from a Printer Class	53
Removing a Printer Class	53
Stopping and Restarting the lp Spooler	54
Other Printing Tasks	55
Controlling the Flow of Print Requests	55
Enabling or Disabling a Printer	55
Controlling the Order of Printing	55
Setting Up the lp Spooler Using SAM	56
Adding a Local Printer	56
Adding a Remote Printer	57
Adding a Network-Based Printer	57
Starting and Stopping the lp Spooler	58
Determining the Status of the lp Spooler	59
Disabling a Printer	59
Enabling a Printer	59
9. Configuring TCP/IP	60
IRIX TCP/IP Networking	60
Setting the Hostname	60
	60
	60
	60
BigDog.hp.com	60
Setting the Subnet Mask	60
Configuring Anonymous FTP Access	60
	60
	60
	60
	60
An anonymous FTP account allows anyone to login to your system as an anonymous FTP user. This can pose a serious security threat and should be done only when the system administrator keeps a careful eye on all anonymous FTP activity to avoid compromising	60
HP-UX TCP/IP Networking	62
The set_parms Script	62
Networking Startup Files	62
Editing the /etc/hosts File	63
The Name Service Switch	63
Choosing a Name Service	64
Configuring Routes	64
To Set the Default Gateway Using SAM	65
Changing a Host’s IP Address	65
Configuring inetd	66
Editing the /var/adm/inetd.sec File	67
Enabling bootp and tftp	67
Start SAM:	67
Configuring rwhod	68
Configuring Logging for the Internet Services	68
syslogd	68
Configuring inetd Connection Logging	69
Configuring ftpd Logging	69
Configuring Anonymous ftp Access	69
Using SAM to Configure Anonymous ftp	71
Restricting ftp Access with /etc/ftpusers	71
Creating /etc/hosts.equiv	71
10. Domain Name Service	73
DNS Under IRIX	73
BIND Configuration Files	73
hoResolution with /etc/resolv.conf	73
Configuring the Primary BIND Server	73
Configuring the Secondary BIND Server	76
Configuring the Name Service Switch	77
DNS Under HP-UX	77
Server Data Files	77
Name Server Startup Files	77
Setting the Default Domain Name	78
Configuring a Primary Master Name Server	78
To Add a Host to the Domain Data Files	79
To Delete a Host from the Domain Data Files	79
Configuring a Secondary Master Name Server	79
Configuring a Caching-Only Name Server	80
Configuring the Resolver to Query a Remote Name Server	80
Starting the Name Server Daemon	81
Configuring the Name Service Switch	82
Default Configuration	83
The /etc/nsswitch.conf File	83
To Check the Current hosts Configuration	83
To Trace a Host Name Lookup	84
Updating Network-Related Files	84
To Update /etc/hosts.equiv and $HOME/.rhosts	84
To Update /var/adm/inetd.sec and $HOME/.netrc	85
To Update /etc/hosts	85
Configuring BIND in SAM	85
Name Server Statistics	85
1	86
11. NIS	86
NIS Under IRIX	86
Setting Up the NIS Master Server	86
Setting the Master Server’s Domain Name	86
Building the Master Maps	86
	87
	87
Name (<Enter> to exit): bigcats	87
Starting NIS on the Master Server	87
Testing the NIS Master Server	87
Setting Up NIS Slave Servers	87
Setting the Slave Server’s Domain Name	87
Binding to Another NIS Server	87
Building the Duplicate Maps	88
Starting NIS on the Slave Server	88
Testing the NIS Slave Server	89
Setting Up NIS Clients	89
Configuring NIS on the Client	89
Starting NIS on the Client	89
Testing the NIS Client	89
NIS Under HP-UX	89
NIS Maps and Commands	89
Normal System Startup	90
Configuring and Administering an NIS Master Server	91
Configuring the NIS Master Server to Use a Private passwd File	91
Configuring and Administering an NIS Slave Server	92
To Edit the Slave Server’s passwd File	92
To Enable NIS Slave Server Capability	93
To Schedule Regular Map Transfers from the NIS Master Server	94
To Add a Slave Server to Your NIS Domain	94
To Remove a Slave Server from Your NIS Domain	95
To Modify an NIS Map	95
Configuring and Administering an NIS Client	96
To Edit the NIS Client’s passwd File	96
To Edit the NIS Client’s group File	97
To Enable NIS Client Capability	97
To Bind an NIS Client to a Server on a Different Subnet	98
To Query BIND for Host Information After Querying NIS	98
12. Network File System	100
NFS on IRIX	100
Setting Up an NFS Client	100
	100
	100
	100
	100
For each NFS directory that you want to mount, add an entry to the /etc/fstab file.	100
Setting Up the Automatic Mounters	100
Setting Up a Default Automatic Mounter Environment	100
NFS on HPUX	101
Installing the NFS Services Software	101
Startup Files	101
Configuring and Administering an NFS Server	101
Exporting directories	101
To Enable NFS Server Capability	102
Unexporting Directories	102
To Disable NFS Server Capability	103
Configuring and Administering an NFS Client	104
# /sbin/init.d/nfs.client stop	106
Automounter	106
Automounter Startup Files	106
Configuring Automounter	106
To Enable the NFS Automounter	106
To Restart the Automounter	107
13. sendmail	108
sendmail Under IRIX	108
Starting the sendmail Daemon	108
Listing the sendmail Message Queue	108
Forcing the sendmail Message Queue	108
sendmail Under HP-UX	109
Installing sendmail on a Standalone System	109
Installing sendmail on a Mail Server	109
Installing sendmail on a Mail Client	110
To Configure a sendmail Client System to Access a sendmail Server:	110
Adding sendmail Aliases to the Alias Database	110
Restarting sendmail	111
Configuring a sendmail Client to Relay All Mail to a Server	111
Using SAM to Install sendmail	112
Manually Installing sendmail	112
Installing a Configuration File	112
Making sendmail Executable	113
Creating System-wide Mail Aliases	113
Invoking the sendmail Daemon	113
Stopping and Starting the sendmail Daemon	114
The Mail Queue	114
The System Log	114
14. The Desktop Environment	116
Introduction	116
The Relationship Between X, Motif, and CDE	116
The X Window System	116
Motif	116
	116
	116
	116
Mwm window manager	116
CDE	116
	116
	116
	116
Workspace Manager	116
The IRIX Desktop Environment	116
X Windows on IRIX	116
The HP-UX Desktop Environment	118
X Windows on HP-UX	118
Files and Directory Structure	118
Unsupported Clients	118
Starting X	119
Examples	120
Stopping X	120
hpterms	121
X, Motif, and CDE Configuration Files	121
X Configuration Files	121
	121
sys.x11start	121
X*screens	121
Motif Configuration Files	122
CDE Configuration Files	122
CDE Under HP-UX	122
What Happens when CDE Starts?	122
Customizing CDE	123
Adding or Removing Objects from the Front Panel	123
CONTROL NewControl	124
KEYWORD Value	124
Adding Objects to Slideup Subpanels	124
SUBPANEL SubPanelName	125

Match case Limit results 1 per page

Domain Name Service

Configuring the Name Service Switch

The Name Service Switch determines where your system will look for the information that is traditionally

stored in the following files:

/etc/hosts

/etc/protocols

/etc/services

/etc/networks

/etc/netgroup

/etc/rpc

For all types of information except

host

information, you can configure your system to use NIS, the local

/etc

file, or both, in any order. For host information, you can configure your system to use BIND (DNS),

NIS, the

/etc/hosts

file, or any combination of the three, in any order. The default Name Service Switch

configuration is adequate for most installations, so you probably do not have to change it.

NOTE: Configuring the Name Service Switch is a separate task from configuring the name services

themselves. You must also configure the name services before you can use them. The Name Service Switch

just determines which name services are queried and in what order. You can use SAM to configure the

Name Service Switch.

The following are some suggestions for customizing your Name Service Switch configuration:

•

If you want your system to consult the local

/etc/netgroup

file when it fails to find a netgroup in the

NIS netgroup database, create or modify the netgroup line in the

/etc/nsswitch.conf

file as follows:

netgroup: nis [NOTFOUND=continue] files

•

If you want your system to consult BIND (DNS) when it fails to find a host name in NIS, create or

modify the hosts line in the

/etc/nsswitch.conf

file as follows:

hosts: nis [NOTFOUND=continue] dns files

•

With this configuration, if NIS does not contain the requested information, and BIND is not

configured, the

/etc/hosts

file is consulted.

•

If you want your system to consult NIS if it fails to find a host name in BIND or if the BIND name

servers are not responding, create or modify the hosts line in the

/etc/nsswitch.conf

file as follows:

hosts: dns [NOTFOUND=continue TRYAGAIN=continue] nis files

With this configuration, if BIND does not return the requested information, and NIS is not running, the

/etc/hosts

file is consulted.

HP recommends that you maintain at least a minimal

/etc/hosts

file that includes important addresses like

gateways, diskless boot servers and root servers, and your host±s own IP address. HP also recommends that

you include the word ²files³ in the hosts line to help ensure a successful system boot using the

/etc/hosts

file when BIND and NIS are not available.

CAUTION: Changing the default configuration can complicate troubleshooting. The default configuration

is designed to preserve the authority of the name service you are using. It switches from

BIND to NIS only

if BIND is not enabled. It switches from NIS to the local

/etc

file only if NIS is not enabled. It is very

difficult to diagnose problems when multiple name servers are configured and enabled for use.