HP-UX System Administrator's Guide: Configuration Management HP-UX 11i Version 3 HP Part Number: 5992-6579 Published: September 2009 Edition: 4
© Copyright 2008, 2009 Hewlett-Packard Development Company L.P. Legal Notices Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Warranty The information contained herein is subject to change without notice.
Table of Contents Preface.......................................................................................................................................11 Intended Audience.............................................................................................................11 About This Series................................................................................................................11 About This Document....................................................................
Setting System and Network Parameters...........................................................................41 Customizing System-Wide and User Login Environments...............................................42 Setting Shadow Password Mode........................................................................................43 To Switch to Shadow Password Mode..........................................................................43 To Switch to Standard Password Mode................................
Sharing a Local Home Directory........................................................................................72 Allowing Access from Remote Systems.............................................................................72 $HOME/.rhosts File.......................................................................................................72 Enabling X Window Server Access...............................................................................73 5 Configuring Networking...............
Telnet......................................................................................................................107 Using Telnet to Log in to a PC from an HP-UX System...................................108 Using Telnet to Log in to an HP-UX System from a PC...................................109 Other Terminal Emulators.....................................................................................110 6 Configuring Printers.....................................................................
Central Mail Hub Topography (Receiving E-mail).....................................................126 Configuring the Hub..............................................................................................127 Configuring the Clients..........................................................................................127 Gateway Mail Hub Topography (Receiving E-mail)...................................................127 Configuring the Hub.......................................................
Other Kernel Configuration Operations...........................................................................156 Common Behavior for Kernel Configuration Commands...............................................157 Common Command Line Options..............................................................................157 Common Output Formats...........................................................................................158 Common Exit Status Codes...............................................
Uses for System Files...................................................................................................194 The Kernel Configuration Log File...................................................................................195 Parsing Command Output...............................................................................................196 Recovering from Errors.....................................................................................................
Preface Intended Audience The HP-UX System Administrator’s Guide series is written for administrators of HP-UX systems of all skill levels needing to administer HP-UX systems, beginning with HP-UX Release 11i Version 3. While many topics in this set apply to previous releases, much has changed in HP-UX 11i Version 3. Therefore, for information about prior releases, please refer to Managing Systems and Workgroups: A Guide for System Administrators.
Chapter 2: “Configuring System Parameters” Starting a preinstalled system and general initialization. Chapter 3: “Configuring Root” Setting up a root user home directory and configuring root user parameters. Chapter 4: “Configuring Users and Groups” Adding users to the system. Chapter 5: “Configuring Networking” Setting up the network interface, sharing directories with other systems, transferring files between systems.
Table 1 Finding HP-UX Information If you need to. . . Refer to . . . Located at . . . Find out: The HP-UX 11i Release Notes • What has changed specific to your version of in HP-UX releases HP-UX. • The content of the Operating Environments • Firmware requirements, and supported systems for a specific release • HP Instant Information • HP Technical Documentation web site http://docs.hp.
Each HP-UX 11i release has an associated release name and release identifier. The uname command with the -r option returns the release identifier. Table 2 shows the releases available for HP-UX 11i. Table 2 HP-UX 11i Releases OS Version Identifier Release Name Supported Processor Architecture B.11.11 HP-UX 11i Version 1 HP 9000 B.11.23 HP-UX 11i Version 2 Integrity B.11.23.0409 HP-UX 11i Version 2 September 2004 Update HP 9000 and Integrity B.11.31 HP-UX 11i Version 3 HP 9000 and Integrity B.
Table 3 OS Version, System Architecture, and Machine Model (continued) Topic Command Sample Output Operating Environment $swlist HPUX*OE* # HPUX11i-OE-MC B.11.31 HP-UX Mission Critical Operating Environment1 OS Version.Update $swlist HPUX*OE* 1 2 3 # HPUX11i-TCOE B.11.23.0409 HP-UX Technical Computing OE Component 1 HP-UX 11i OS version identifiers have the form B.11.23 or B.11.23.0409, where B.11.23 is the OS version and 0409 is the year-month of the operating environment (OE) update.
Examples and Shells This document describes practices used by the system administrator. Since the root user (a superuser) is required to use the POSIX shell /sbin/sh, all command examples use that shell. The POSIX shell is defined in sh-posix(1). For information on other shells, see the Shells User’s Guide and sh(1). Command Syntax Literal A word or character that you enter literally. Replaceable A word or phrase that you replace with an appropriate value.
The general definition form is: type func ( type param [, type param]... ); For example: int setuname ( const char *name , size_t namelen); The usage form is: func ( param [, param]... ); For example: setuname ( name , namelen ); The function syntax elements are the same as for commands, except for the options. Publication History The document publication date and part number indicate its current edition. The publication date will change when a new edition is released.
NOTE: The volumes in the HP-UX System Administrator’s Guide may be updated independently. Therefore, the latest versions of the volumes in the set may vary with time, with respect to each other. The latest versions of each volume are available at http://docs.hp.com.
1 Introduction The HP-UX System Administrator’s Guide: Configuration Management continues where the HP-UX 11i V3 Installation and Update Guide leaves off. It describes the process of preparing your system for use and connecting it into the local network. Topics include: • • • • • • • • • • Initial start-up of a preinstalled system (called instant ignition). See “Starting A Preloaded System” (page 35). Initial configuration of system parameters. See “Setting System and Network Parameters” (page 41).
HP-UX System Management Homepage (Web-Based) The HP-UX System Management Homepage (HP SMH) is a web-based interface that manages one HP-UX system at a time. It completes the transfer of the System Administration Manager (SAM) functions into web-based processes. In HP-UX 11i Version 2, the SAM functional areas for kernel configuration, peripheral devices, and partition management became web-based, using kcweb, pdweb, and parmgr, respectively.
Many HP SMH procedures provide the option to preview the HP-UX commands that they will use to perform the task at hand. HP-UX System Management Homepage (Web-Based) The HP-UX System Management Homepage (HP SMH) helps you with detailed system administration. When you log in via the web (see “Starting an HP SMH Web Client” (page 24)), you see a Home page that gives you access to a wide range of system information and some principal areas of system configuration.
See “Authenticating Users with PAM” in HP-UX System Administrator’s Guide: Security Management. • Disks and File Systems Disks File Systems Logical Volumes Paging Space Volume Groups See HP-UX System Administrator’s Guide: Overview, HP-UX System Administrator’s Guide: Logical Volume Management, and VERITAS File System 3.5 (HP OnlineJFS/JFS 3.5) Administrator's Guide manuals, and The Next Generation Mass Storage Stack white paper.
Alarms Modules Tunables See “Configuring the Kernel in the HP-UX System Administrator’s Guide: Configuration Management.
• Printer Management(web-based) Configure Printers or Plotters Manage Print Requests Save or Restore Print Spooler Configuration See “Configuring Printers” in the HP-UX System Administrator’s Guide: Configuration Management. • Resource Management Event Monitoring Service • Serviceguard Serviceguard Manager See the Managing Serviceguard manual.
After a brief wait, you will see the login web page for HP SMH. Enter a valid HP SMH login name (for example, root) and the password. https://targetsystem:2381/ • • If the hpsmh daemon is running on the target system, you will see the login web page for HP SMH. Enter a valid HP SMH login name (for example, root) and the password.
See the HP-UX System Administrator’s Guide: Security Management. • c - Security Attributes Configuration Topics include password aging and default umask. — s - System Defaults Configure system-wide values of security attributes. See security(4). — l - Local Users Configure per-user values of security attributes of local users (if NIS is not configured). See userdb(4). See “Configuring System and User Security” in the HP-UX System Administrator’s Guide: Configuration Management.
— v - Volume Groups View or Manage Volume Groups — d - Disks View or Manage Disk Devices See HP-UX System Administrator’s Guide: Overview and HP-UX System Administrator’s Guide: Logical Volume Management.
(Also accessible with /usr/sbin/kcweb -t) • l - Printers and Plotters(new) — p - printers — r - print requests — s - spooler configuration — a - add printer — c - show common problems • m - Event Monitoring Service — q - requests — r - resources • n - Networking and Communications — s - Network Services Configuration ◦ b - Bootable Devices – b - DHCP Device Groups Booting from This Server – r - Devices for which Boot Requests are Relayed to Remote Servers – f - Fixed-Address Devices Booting from This S
n - Netgroups ◦ ◦ – Local Netgroups r - Routes c - System Access i - Internet Services r - Remote Logins ◦ t - Time s - System Clock b - NTP Broadcasting n - NTP Network Time Sources See “Configuring Networking” in the HP-UX System Administrator’s Guide: Configuration Management. See also NFS Services Administrator's Guide. (Also accessible with /usr/sbin/ncweb -t) — i - Network Interfaces Configuration ◦ a - Auto Port Aggregation ◦ n - Network Interface Cards See HP-UX LAN Administrator's Guide.
— m - Remove Depot Software — d - Interactive List, Depot Software — u - Update HP-UX Operating Environment • u - Accounts for Users and Groups — l - Local Users View or Configure Local Users (if NIS is not configured). — g - Groups View or Configure Groups. — t - Templates View or Configure User Templates. See “Configuring Users and Groups” in the HP-UX System Administrator’s Guide: Configuration Management.
NOTE: The -t option is not available for /usr/sbin/smh. If the X Window interface is not available, the modules use the alternate text graphic display. • To start text-based HP SMH without the X Window interface, you must unset the DISPLAY environment variable. For example, you can enter the following: # ( unset DISPLAY ; /usr/sbin/smh ) This unsets the DISPLAY variable while HP SMH executes. When HP SMH ends, the value of DISPLAY is restored.
• • To disable an area, highlight it and press d. To disable all areas, press D. You can repeat these operations in any combination. The changes are displayed each time you press a key. 5. 6. 7. Press s to save the changes. Press Esc to return to the previous screen. Press x to exit from the program. User and group privileges are managed separately. Group privileges apply to all users for which it is their primary group, as shown in /etc/passwd.
Setup for a Non-HP-UX Client System If you are logged in to the target system from a non-HP-UX client system, you need to do the following: • • On your non-HP-UX client system, start your X Window server and determine your IP address. This is often available in the Help About menu item of the program screen. If the client is connected to an HP-UX system, the command echo $DISPLAY will show the IP address.
2 Configuring System Parameters This chapter describes the process of starting a preloaded system and setting general system parameters.
Press Return to use the default values. To provide missing information later, log in to a terminal as superuser and execute the command /sbin/set_parms. See “Setting System and Network Parameters” (page 41). 3. Specify a root password. The user name for the superuser is root. The system completes its start-up sequence and displays the desktop login screen. 4. 5. 6. 7. 8. Log in as root for your first session. Establish the environment for the root user. See “Configuring Root” (page 47).
# /usr/sbin/ch_rc -a -p # /usr/sbin/ch_rc -a -p NOLOGIN=1 /etc/default/security NOLOGIN=0 /etc/default/security Changing Login Special Characters As many users discover to their frustration, UNIX was originally developed on TeleType machines that had no backspace operation. Consequently, the process of editing input data was performed by printing characters: #, delete one character and @, delete the line. Interrupt was defined as Rubout (ASCII DEL).
use the new settings. In order to reset the system console, you must reboot the system. See getty(1M) for details. To set /dev/ttyconf every time the system boots, add the stty command to /etc/ inittab.
# who -r . run-level 3 Mar 5 12:01 3 0 S You can add to and change the sequence of processes that HP-UX starts at each run-level. For more information, see the HP-UX System Administrator’s Guide: Overview. Also see the inittab(4) manpage. A superuser logged in at the system console can also change the current run-level with the /sbin/init and /sbin/shutdown commands, as follows: 1. 2. Warn all users who are currently logged in.
Setting the System Clock Only a superuser (root) can change the system clock. The system clock budgets process time and tracks file access. Potential Problems When Changing the System Clock The following are potential problems you can cause by changing the system clock: • • • The make program is sensitive to a file’s time and date information and to the current value of the system clock.
NOTE: HP strongly recommends that you use single-user mode when changing the system clock. Therefore, warn users of a planned system shutdown. See the HP-UX System Administrator’s Guide: Routine Tasks for details on system shutdown. CAUTION: Changing the date while the system is running in multiuser mode may disrupt user-scheduled and time-sensitive programs and processes.
NOTE: If a system is having trouble communicating with other systems, check that /etc/rc.config.d/netconf, /var/adm/inetd.sec, and /etc/hosts files all contain the correct official host name. Table 2-1 The set_parms Keywords Keyword Description initial Run the entire initial boot-time dialog sequence, in the order hostname, timezone, date_time, root_passwd, ip_address, addl_network. hostname Set your unique system or “node” name.
User login scripts can be used to override the system defaults. When HP SMH or useradd adds a user, default user login scripts are copied to the user’s home directory from the skeleton directory, which defaults to /etc/skel. See “Changing the Skeleton Directory” (page 54). The POSIX and Korn shells use .profile. The C shell uses .login and .cshrc. See the Shells: User’s Guide and the Technical Addendum to the Shells: User’s Guide for information on customizing user login scripts.
Setting Long Host Names If the kernel tunable expanded_node_host_names is off (0), the maximum host node name length is eight characters (for example, hprdc185) and the maximum full host name length is 64 characters (for example, hprdc185.example.com). If it is on (1), the maximum for both is 255 characters. By default, this tunable is off. See expanded_node_host_names(5) for details. Setting Long File Names The convertfs command changes an existing file system to long file names.
5. Add the names of any other hosts that you need to reach. If you will be using a BIND or NIS server on a different host, add the name of that host. If your site uses DNS (Domain Name Service) or NIS (Network Information Service), /etc/hosts acts as a backup resource in case the name server goes down; so it is a good idea to add the names of systems that the local system frequently needs to reach.
3 Configuring Root Traditionally, the HP-UX root user, or superuser, has used the system’s root directory, /, as its home directory. This means that root’s supporting files, such as .profile, .kshrc, and .sh_history, are mixed in with file system mounts and other public data. HP recommends that you create a separate home directory for root.
IMPORTANT: Points of interest: • The root entry must be the first line of the /etc/passwd file. • The user ID in field 3 is 0. • Conventionally, the group ID in field 4 is 3 for group sys. • The system entry in field 5 can identify which root user on printouts to networked printers. • The absolute home directory is in field 6. • The login shell in field 7 must be /sbin/sh. 3. 4. When NIS is configured, run /var/yp/ypmake to build or synchronize the passwd maps.
4 Configuring Users and Groups You can control who has access to your system, its files, and its processes. Authorized users gain access to the system by supplying a valid user name (login name) and password. Each user is defined by an entry in the file/etc/passwd. You can use HP SMH to add, remove, deactivate, reactivate, or modify a user account. For additional information about passwords, refer to passwd(4) and passwd(1).
Adding a User with Text-Based HP SMH Use this procedure to add a new user. If you are adding a number of users with the same basic characteristics, consider using a template. See “Making User Templates with Text-Based HP SMH” (page 55) and “Using a Template to Add a User with Text-Based HP SMH” (page 55). 1. 2. Start HP SMH, as described in “Starting Text-Based HP SMH” (page 30). Press u to select Accounts for Users and Groups. 3. Press l to select Local Users or press n to select NIS Users. 4. 5.
(passwd field 6) 9. Create Home Directory If you want HP SMH to create the home directory, set Create Home Directory to Yes. If not, set it to No. 10. Start-Up Program Options Choose a login shell. If you check Select Start-Up Program, the Start-Up Program field offers a list of shells to choose from.
Enable Account Aging The following fields are displayed: Number of Days of Account Inactivity Allowed : -1_________________ Enter the number of days the account can go without a login. If the time between logins is exceeded, the account is disabled. The value -1 disables this restriction. (shadow field 7) Account Lifetime (mm/dd/yy) : ___________________ Enter the expiration date in two-digit month/day/year format. When that date is passed, the account is disabled.
Number of Days to Warn Before Password Expires (0-434 Days): 0__ Displayed only in Shadow Password mode (see “Setting Shadow Password Mode” (page 43)). Enter a value in the range and less than or equal to the Max Time value. When this warn limit is reached, a message is displayed every time the user logs in; for example: Your password will expire in 77 days.
18. When the process completes, you are returned to the Local User or NIS User listing. Skeleton Directory The skeleton directory contains files that are copied to a new home directory by HP SMH and the useradd command. The default skeleton directory is /etc/skel. Files can be added and removed. A different directory can be used; see “Changing the Skeleton Directory” (page 54). The default files in /etc/skel are shown in Table 4-1. Table 4-1 Default Files in the Skeleton Directory File Name Purpose .
Using a Template to Add a User with Text-Based HP SMH Use this procedure to add a new user with the assistance of an HP SMH user template. If you need to define a template, go to the procedure at “Making User Templates with Text-Based HP SMH” (page 55), then return here. 1. 2. Start HP SMH, as described in “Starting Text-Based HP SMH” (page 30). Press u to select Accounts for Users and Groups. 3. Press t to select Templates.
These templates are available to both web-based and text-based HP SMH. They can be made with either version. The following instructions described the text-based process. 1. 2. Start HP SMH, as described in “Starting Text-Based HP SMH” (page 30). Press u to select Accounts for Users and Groups. 3. Press t to select Templates. 4. 5. Press a to select Add User Template. At Template Name, enter a name for the template of up to 16 characters. This is displayed on the template menu and when you add a user.
15. At Account Aging Options, make the selections as described in Step 12 of “Adding a User with Text-Based HP SMH”. This information is stored in the template but is used only if Shadow Password mode is set when the user is added. 16. At Password Aging Options, make the selections as described in Step 13 of “Adding a User with Text-Based HP SMH”. 17. At Security Options, select one of the following: Use System-Wide Values for The system-wide security attributes will be applied to the new account.
5. You can modify the following data by typing in new values or making different selections. See “Adding a User with Text-Based HP SMH” (page 50) for details on the fields and selections. • Login Name • User ID • Allow Duplicate User ID • Primary Group • Home Directory • Create Home Directory • Login Shell • Comments • Account Options • Password Options 6. (Optional) Select Preview to see the commands that will modify the account. Press OK to continue.
Leave Files Undisturbed None of the files or directories owned by the user on the system will be modified, except that listings will show the user ID, not the user name. Remove from User's Home Directory Only All the files owned by the user beneath the user’s home directory will be deleted. The home directory and subdirectories owned by the user will be deleted if they are empty.
5. Group Name Enter the group name. This must start with a letter. The maximum length can be 16 or 255 characters, depending on whether long group names are set. See “Setting Long User and Group Names” (page 43). (group field 1) 6. Group ID Select a numeric group ID. If you mark Next Available ID, HP SMH will select the next available user ID after 100 (not the next ID after the current highest ID). If you mark Specify ID, a. b. A space is displayed for you to type in the number.
username is the login name for the new user. Some of the options are described in Table 4-3. For all the options and complete information on the command, see useradd(1M). Table 4-3 useradd Options Option Meaning -b b_dir Default base directory for user home directory. The default is /home. -c "comments" Full name or other comments. This is often a comma-separated string in the form: fullname,location,workphone,homephone -d dir Home directory path name. The default is b_dir/username.
1. Add the user to the/etc/passwd file. As root, use the/usr/sbin/vipw command to edit /etc/passwd. See vipw(1M), passwd(4), and passwd(1). For example, you might want to add this line for user tom: tom:*:102:20:Tom,,,:/home/tom:/usr/bin/sh This creates the entry and disables logins (the * in the password field). The home directory is /home/tom and the login shell is /usr/bin/sh. The user ID is 102 and the primary group ID is 20, conventionally, users. 2.
Configuring System and User Security Configuring System Default Security Attributes 1. Start HP SMH: • Using the web-based version of the HP SMH: a. Use the URL: http://your_system:2301 to start the web-based interface in your browser. b. Log in using the user name and password of an account with the appropriate privleges (usually root) • 2. Using the text-based interface: a. Enter the command: /usr/sbin/secweb -t to start the text-based interface.
Figure 4-1 Security Attributes Configuration: System Defaults -----------------------------------------------------------Attribute Default Value ============================================================ ABORT_LOGIN_ON_MISSING_HOMEDIR 0 ALLOW_NULL_PASSWORD 1 AUDIT_FLAG 1 AUTH_MAXTRIES 0 BOOT_AUTH 0 BOOT_USERS root DISPLAY_LAST_LOGIN 1 INACTIVITY_MAXDAYS 0 LOGIN_TIMES Any MIN_PASSWORD_LENGTH 6 NOLOGIN 0
5. To modify the value: • Using the web-based version of the HP SMH: With the desired attribute highlighted (you clicked on it), select » Modify System Value ... on the right-hand side of the display. A new page will be displayed with the description and current value for the attribute. Enter a new value for the attribute and click on the Modify button at the bottom of the display. NOTE: To preview what command will be executed by HP SMH before you click on Modify, you can click on Preview.
Displaying Local Users Name User Id User Values ====================================== adm 4 no allanp 1834 no anewuser 111 yes bin 2 no 4. Highlight a user and press Enter. The table in Figure 4-2 is displayed. It shows the attribute name, the current setting for the user (- means the system value), and the current system value. System defaults are marked with the word Default and the default value in parentheses, as in Default (1). The individual attributes are described in the security(4) manpage.
(Description) -------------------------------------------------------------------ALLOW_NULL_PASSWORD [0...1 , 1 ]: default____________ (Allow login with null password? (0=No 1=Yes)) ... UMASK [0...511, 0 ]: default____________ (Default umask (leading zero denotes octal value)) [ Modify ] [ Preview ] [ Cancel ] [ Help ] 7. 8. Make the changes you want in the spaces provided. (Optional) Select Preview to see the commands that will modify the attributes. Press OK to continue. 9.
Setting File Access Permissions The /usr/bin/chmod command changes the type of access (read, write, and execute privileges) for the file’s owner, group members, or all others. Only the owner of a file (or the superuser) can change its read, write, and execute privileges. For details, see chmod(1). By default, new files have read/write permission for everyone (-rw-rw-rw-) and new directories have read/write/execute permission for everyone (drwxrwxrwx).
POSIX shell users /etc/skel/.profile is copied to the home directory as .profile. For C shell users, /etc/skel/.login and /etc/skel/.cshrc are copied to the home directory as .login and .cshrc. Refer to the Shells: User’s Guide and the Technical Addendum to the Shells: User’s Guide for information on customizing user login scripts. NOTE: Do a full backup once you have initially set up and customized your system.
Local versus Remote Home Directories Users can have their home directory on their own local system or on a remote file server. The advantage of keeping all users’ home directories on one file server is that you can back up all the accounts at one time. If a user’s home directory is on a remote server, you may want to create a minimal home directory on the local system so that a user can still log into the local system if the server is down.
Next, create an account for Tom on the file server, flserver. See “Configuring Users and Groups with HP SMH” (page 49). Then, perform the following procedure: 1. On the file server, share Tom’s home directory and the directory where he does his work: a. Add an entry in the /etc/dfs/dfstab file to share Tom’s home directory: share -F nfs -o access=appservr:dept27:wsj6700 /home/tom If the directory is already shared, simply add Tom’s system to the access list. b.
See “Sharing an HP-UX Directory” (page 77) for more information. Sharing a Local Home Directory Assume you are setting up an account on the system named wsj6700 for the user lisa. In this example, lisa’s home directory will reside on her local disk and will be shared with the other systems she logs in to. 1. On the local system, do the following: a. Create the user’s account. See “Configuring Users and Groups with HP SMH” (page 49). b.
In the following example, /users/spence/.rhosts resides on system wsj6700. Users tom and patrick can log in to spence’s account on wsj6700, from dept27 and wsb2600 respectively, without supplying a password. dept27 tom wsb2600 patrick Enabling X Window Server Access To allow an X Window client to send output to an X Window server using the display option, use the xhost command. For example, to allow system dept27 to send a window to system wszx6, enter: xhost +dept27 on system wszx6.
5 Configuring Networking This chapter describes the following networking topics: • • • “Configuring the Network File System (NFS)” (page 75) “Configuring File Transfer Protocol (FTP)” (page 87) “Interfacing with Microsoft Windows Systems” (page 106) Other networking issues are described in: • • “Setting System and Network Parameters” (page 41) “Ethernet Configuration and Verification” (page 135) Configuring the Network File System (NFS) This section provides procedures and troubleshooting information fo
Beginning with HP-UX 11i v3, file systems are “shared” with other systems with the share command. Shared file system information is stored in the /etc/dfs/dfstab file. For conversion information, see the HP-UX 11i Version 3 Release Notes. Enabling and Disabling the NFS Server and Client The following procedures describe how to enable or disable the NFS server and client. Enable or Disable the NFS Server with Text-Based HP SMH 1. 2. 3. Log in to the server as superuser.
Sharing an HP-UX Directory Use either of the following procedures to set up NFS shares on the server. • • “Share a Directory Using Text-Based HP SMH” (page 77). “Share a Directory Using HP-UX Commands” (page 77). NOTE: An NFS server can share an ordinary file as well as a directory. In either case, the NFS client must mount the shared file system on a directory. Share a Directory Using Text-Based HP SMH 1. 2. 3. 4. Log in to the server as superuser.
2. If the system is not already configured as an NFS server: a. Edit /etc/rc.config.d/nfsconf, setting the following values: NFS_CORE=1 NFS_SERVER=1 START_MOUNTD=1 NOTE: You can also use the setoncenv command to set and display NFS and other Open Network Computing configuration variables. See setoncenv(1M). b. Run the nfs.server script: # /sbin/init.d/nfs.server start 3. Edit /etc/dfs/dfstab, adding an entry for each directory that is to be shared.
NOTE: Files in the local directory will be hidden, but not overwritten, when you mount the remote directory. The local files will be accessible again once you unmount the remote directory. • Make sure that the client has permission to share the file system from the server. This requires an entry in /etc/dfs/dfstab on the server; see Step 3 under “Share a Directory Using HP-UX Commands” (page 77). • Decide what type of mount you want. See Table 5-1: “Deciding Which Type of NFS Mount to Use” (page 80).
Table 5-1 Deciding Which Type of NFS Mount to Use You can use a standard NFS mount or the NFS automounter. Standard NFS Mount— Use a standard NFS mount when you would like the mounted file system to always remain mounted. This is useful when the mounted file system will be frequently accessed. Automounted NFS— Use an automatically mounted NFS file system when you want the file system to be mounted only when it is actively being used. This is useful when the file system being mounted is used infrequently.
a. b. c. Press f, Disks and File Systems. Press f, File Systems - View or Manage File Systems. Press n, Add NFS. The Add A New NFS File System screen is displayed 5. Fill in the fields. (The default values are marked.) • Mount Point: The full name of the local directory. • Remote Server: The full name of the system sharing the file system. • Remote Directory: The full name of the shared file system. • Mount method: Check one.
Automount a Shared File System Using Text-Based HP SMH NOTE: The Disks and File Systems functional area performs standard mounts. The Networking and Communications functional area performs automounts. 1. 2. 3. 4. Log in to the client as superuser. Start HP SMH, as described in “Starting Text-Based HP SMH” (page 30). Enable the NFS client, if necessary, as described in “Enabling and Disabling the NFS Server and Client” (page 76). Navigate to the Networked File Systems (Automounter) screen. a.
NOTE: If the directory does exist, its contents will be hidden when you mount the remote directory, and will not be usable until you unmount it. 4. Add an entry to/etc/fstab so the file system will be automatically mounted at boot time. nfs_server:/nfs_server_dir /client_dir nfs options 0 0 For example: fancy:/opt/adobe /opt/adobe nfs defaults 0 0 5. Mount the remote file system.
Troubleshooting NFS Table 5-2 outlines some troubleshooting techniques for common NFS problems. Table 5-2 Troubleshooting NFS Problem What To Do Individual client can’t Verify the following on the client: import from one or • The local directory exists on the client. If it does not exist, create it using mkdir. more servers For example: # mkdir /opt/adobe • LAN cable is intact and connected, and all connections are live. • /etc/hosts exists and has “Requisite Entries” (page 85).
Table 5-2 Troubleshooting NFS (continued) Problem What To Do Stale NFS file handle On the clients: • Use the rmsf command with the -x and -H options to remove stale device special files. For details, see rmsf(1M). This is common on NFS clients after a server has crashed, or been rebooted before clients have unmounted NFS file systems, or after /etc/dfs/dfstab has been changed on the server. or … • Ensure that there are no open files in the affected file systems; then try unmounting and remounting them.
Recovering Network Services after a Power Failure This section describes how to troubleshoot problems you and your system users are likely to encounter when rebooting after a general power failure or outage. The examples assume you are using DNS (Domain Name Service). Symptoms and Keywords RPC_PROG_NOT_REGISTERED name_server rcmd: hostname: Unknown host rcmd:hostname: Not in database rcmd:hostname: Access denied What To Do A.
Moving or Reusing a Shared Directory If you rename an NFS-mounted directory, NFS clients must unmount and remount the imported directory before they can see the new contents. For example, if a server is sharing /opt/myapp, and you move /opt/myapp to /opt/ myapp.
6. Select Enable. HP SMH executes commands that create a password entry in the appropriate files, creates the ftp user account, and sets up the needed files and programs.
# chown root /home/ftp/usr # chmod u=rx,g=rx,o=rx /home/ftp/usr 5. Create the subdirectory etc under the ftp directory: # cd /home/ftp # mkdir etc 6. Copy /etc/passwd and /etc/group to /home/ftp/etc. These files are required by the ls command, to display the owners of files and directories under /home/ftp. # cp /etc/passwd /home/ftp/etc # cp /etc/group /home/ftp/etc 7.
12. Change the owner of user ftp’s home directory to root and the permissions to not writable (mode 0555): # chown root /home/ftp # chmod u=rx,g=rx,o=rx /home/ftp Troubleshooting FTP Login Symptom: Some or all users can’t ftp to an HP-UX system. If no users can ftp to a given system, check first of all that inetd is running on that system: # ps -ef | grep inetd If inetd is not running, start it: # /usr/sbin/inetd It is also possible that the FTP service is disabled. Check /etc/inetd.
Configuring HP-UX Systems for File Transfer Transferring files between computers is a common workgroup activity. When you’re mixing HP-UX systems and PCs in a workgroup, network transfers are usually the most efficient, and sometimes the only, way to transfer files from one type of system to another. Many HP-UX systems are not equipped with floppy disk drives, and many PCs are not equipped with DDS drives or other external file storage peripherals often found on HP-UX systems.
ftp> open vectrapc1.net2.corporate If the connection is successful, FTP will let you know that you are connected and display information about the PC’s FTP server: Connected to vectrapc1.net2.corporate. 220 vectrapc1 Microsoft FTP Service (Version 2.0). If your connection succeeded, proceed to Step 3. If it fails, use Table 5-3 (page 93).
Table 5-3 Troubleshooting the FTP Connection to a PC TROUBLESHOOTING INFORMATION If the connection is not successful, FTP will let you know that the connection failed. The displayed error message will vary depending on what is the cause of the failed connection: □ ftp: connect: Connection refused The most likely cause of this message is: – Problem: The FTP publishing service on the Windows NT-based PC is not running (has not been started). Solution: Start the FTP server on the PC.
3. Enter login information When you have successfully connected to your PC, another message will follow the Connected to... message: Name (vectrapc1.net2.corporate:userx): This message is actually a login prompt, and there are several ways to respond to it: • Press Return to accept the default response. In the above example, there are three parts to the displayed prompt: 1. The word Name 2. The network name for your PC (vectrapc1.net2.corporate) 3.
Name (vectrapc1.net2.corporate:userx): anonymous You will then be prompted to enter a password in a special way: 331 Anonymous access allowed, send identity (e-mail name) as password. Instead of entering the actual password for an account, enter your e-mail address as a way of identifying yourself to the FTP server: Password: userx@net2.
2. Determine whether the file you are trying to transfer is an ASCII (text) file or a binary (non-ASCII) file and set the transfer mode accordingly: a. For ASCII files, set the transfer mode using FTP’s ascii command: ftp> ascii This enables character conversions such as end-of-line carriage return stripping to occur. b. For binary files (graphics files, sound files, data base files, etc.
1. Locate the file you want to send. You can use FTP’s lcd and ! (execute a local shell command) commands to locate the file on your local system if it is not in the directory that was your current working directory at the time you started ftp. Also, if the file is not in your current directory, you can specify a full (absolute) path name for the file you want to send to your PC.
2. Determine whether the file you are trying to transfer to your PC is an ASCII text file or a binary (non-ASCII) file and set the transfer mode accordingly: a. For ASCII (plain text) files, set the transfer mode using FTP’s ascii command: ftp>ascii This enables character conversions such as those that handle the differences between how the ends of lines are handled between differing types of operating systems. b. For binary files (graphics files, sound files, data base files, etc.
Establishing an FTP Connection from a PC to HP-UX NOTE: See also “Establishing an FTP Connection from HP-UX to a PC” (page 91). If you have a third-party program, use those instructions instead. 1. On your PC, start the FTP utility: a. Click the Start bar in the lower-left corner of your PC’s screen. b. Click Programs in the pop-up menu. c. Click Accessories in the next pop-up menu. d. Click Command Prompt in the final pop-up menu. e. Type ftp at the prompt in the window. 2.
to have inetd reread its configuration file. □ ftp: connect: Connection timed out Possible causes of this error message include: – Problem: Your HP-UX system is not currently running. Solution: Make sure your HP-UX system is turned on, and running (the system has been booted). – Problem: Your HP-UX system is not currently reachable on the network.
3. Enter login information When you have successfully connected to your HP-UX system, another message will follow the Connected to... message: Name (flserver.net2.corporate:(none)): This message is actually a login prompt, and there are two ways to respond to it: • Enter a valid account name and password for your PC. You will then be prompted to enter the password for the account. If after noting the following caution you feel comfortable doing so, enter the account’s password.
On the PC: Retrieving a File from the HP-UX System Once you have made a connection and logged in to your HP-UX system from your PC (See “Establishing an FTP Connection from a PC to HP-UX” (page 99)) you are ready to retrieve a file from the HP-UX system. 1. Locate the file you want to retrieve from your HP-UX system. You can use FTP’s cd and ls commands pretty much as you would in an HP-UX shell (sh, ksh, csh, etc.).
2. Determine whether the file you are trying to transfer is an ASCII file or a binary (non-ASCII) file and set the transfer mode accordingly: a. For ASCII (plain text) files, set the transfer mode using FTP’s ascii command: ftp>ascii This enables character conversions such as end-of-line carriage return stripping to occur. b. For binary files (graphics files, sound files, database files, etc.
On the PC: Sending a File to the HP-UX System Once you have made a connection and logged in to your HP-UX system (See “Establishing an FTP Connection from a PC to HP-UX” (page 99)), you are ready to transfer a file to the your HP-UX system. 1. 104 On your PC, locate the file you want to send. You can use FTP’s lcd and ! commands to locate the file on your local system if it is not in the directory that was your current working directory at the time you started ftp.
2. Determine whether the file you are trying to transfer to your HP-UX system is an ASCII file or a binary (non-ASCII) file and set the transfer mode accordingly: a. For ASCII (plain text) files, set the transfer mode using FTP’s ascii command: ftp>ascii This enables character conversions such as those that handle the differences between how the ends of lines are handled between differing types of operating systems. b. For binary files (graphics files, sound files, database files, etc.
Interfacing with Microsoft Windows Systems The following topics describe the process of adding PC/NT systems into a work group.
HP CIFS HP CIFS provides HP-UX with a distributed file system based upon Microsoft’s CIFS (Common Internet File System) protocol, also known as the SMB (Server Message Block) protocol. The SMB protocol is the native file-sharing protocol in Microsoft Windows and OS/2 operating systems and is the standard way that millions of PC users share files across corporate intranets. HP CIFS implements both the server and client components of the CIFS protocol on HP-UX.
Using Telnet to Log in to a PC from an HP-UX System To use Telnet to log in to a personal computer from your HP-UX system, you will need to: 1. Make sure that the PC is running, and reachable via your network. a. Turn on the PC and boot up the Windows NT operating system. b. Make sure that your PC has networking services configured, and has a network address (IP Address). 2. Make sure that the PC is running Telnet server software. a. Install a version of Telnet server software.
Using Telnet to Log in to an HP-UX System from a PC 1. Make sure that the PC is running, and reachable via your network. a. Turn on the PC and boot up the Windows NT operating system. b. Make sure that your PC has networking services configured, and has a network address (IP address). 2. Make sure that the telnetd daemon is running on your HP-UX system. The telnetd daemon is not usually run directly.
Other Terminal Emulators Telnet is only one of many terminal emulators — sometimes known as virtual terminals — that can be used to log in to remote systems, but in the UNIX world it is a common one. Another that is often supported by software packages on the PC for interacting with UNIX systems is rlogin. The rlogin daemon on HP-UX systems is rlogind. The setup and use of rlogin between HP-UX systems and PCs is quite similar to that for Telnet, especially on the HP-UX end.
6 Configuring Printers Printers can be connected in three ways: • Local: physically connected to the system. • Remote: physically connected to another system. • Network: installed as a domain on a LAN.
To add a printer to the spooler, see “Adding a Local Printer to the LP Spooler” (page 112), “Adding a Remote Printer to the LP Spooler” (page 113) or “Adding a Network Printer with HP JetDirect” (page 116). Starting and Stopping Spooler Using Text-Based HP SMH 1. 2. 3. As a privileged user, start text-based HP SMH. See “Starting Text-Based HP SMH” (page 30). You can invoke it with or without the X Window interface. Press p, Printers and Plotters. Highlight and select Printers and Plotters.
3. If the printer being added will be the default printer, execute the following: # /usr/sbin/lpadmin -dlocal_printer Allow print requests to be accepted for the newly added printer. For example: # /usr/sbin/accept local_printer 4. Enable the newly added printer to process print requests. For example: # /usr/bin/enable local_printer 5. Start the LP spooler if it is not already running: # /usr/sbin/lpsched 6. Test the printer using the LP spooler, then check the LP spooler’s status.
• Remote Printer is on a BSD system Check the box if the remote operating system is BSD. • Remote Cancel Name The default is rcmodel. • Remote Status Name The default is rsmodel. • Default Request Priority This is the minimum priority (fence) that a print job must have in order to print on this printer. 0 is the lowest. • Allow Anyone to Cancel a Request Check the box if you want to allow anyone, not just the owner or a superuser, to cancel print requests for this printer.
3. Allow print requests to be accepted for the newly added remote printer. For example: # /usr/sbin/accept local_printer 4. Enable the newly added printer to process print requests. For example: # /usr/bin/enable local_printer 5. If the printer being added will be the default printer, execute the following: # /usr/sbin/lpadmin -dlocal_printer 6. Start the LP spooler if it is not already running to process print requests. # /usr/sbin/lpsched 7. Send a sample print job to the printer.
Adding a Network Printer with HP JetDirect The HP JetDirect software must be installed on your system. With HP JetDirect, printers can connect directly to the network. The printer uses a LAN connection and the HP JetDirect software transmits print requests. For more information, see the HP JetDirect Network Interface Configuration Guide. Follow the instructions shipped with your printer or the network interface card for the printer. See also the jetadmin(1) manpage.
1. As a superuser, enter the command, # /opt/hpnp/admin/jetadmin 2. 3. 4. 5. Enter 1 to choose option 1) Configuration (super-user only). Enter 3 to choose option 3) Add printer to local spooler. Enter the full domain name of the network printer or its IP address. For example, printer3.myhost.example.com or 192.0.34.166. On the Configurable Parameters list, enter 1 to choose item 1) Lp destination (queue) name and assign the printer a unique local name (to be used in printing operations, such as lp).
4. Start the LP spooler if it is not already running: # /usr/sbin/lpsched Removing a Printer from the LP Spooler These procedures can be used to remove local, remote, and network printers from the spooler. Removing a Printer Using Web-Based HP SMH 1. 2. 3. 4. Ensure that an X Window System server is running on your local system. See “Using the X Window System” (page 32). Start web-based HP SMH from your local system. See “Starting an HP SMH Web Client” (page 24).
Users will see the message Use alternate printer when they direct requests to a rejected destination if the printer has not been removed. Once the printer has been removed and users try to send a request, they will see the message Destination printer_name non-existent. 5. (Optional) Determine if there are any jobs in the printer’s queue. For example: # /usr/bin/lpstat -o laser1 6. (Optional) Disable the printer to be removed. For example: # /usr/bin/disable -r"Printer laser1 is disabled.
Removing a Printer Class NOTE: When you remove a printer class, the printers in the class are not removed — you may still use them as individual printers. If you remove all printers from a class, that printer class is automatically removed. You cannot use HP SMH to remove a printer class. Removing a Printer Class Using HP-UX Commands See reject(1M), lpmove(1M), lpadmin(1M), and lpsched(1M) for details on the command options. 1. 2. Ensure that you have superuser capabilities.
7 Configuring Mail Whether you are administering a single system or a workgroup containing many systems, you will probably want your users to be able to communicate with each other using electronic mail (e-mail). This topic area will help you understand what is involved in setting up e-mail services for your workgroup.
mail. On HP-UX and other UNIX systems, the primary Mail Delivery Agent is sendmail. Although sendmailcan be run directly from a shell command line to send a message, it is not usually used in this way. Mail User Agents are usually used as front ends to sendmail for sending mail.
Networking Topographies Although there are many ways to configure electronic mail for a group of computers under your control, the following setups are often used: □ □ □ Central Mail Hub Gateway Mail Hub Fully Distributed Central Mail Hub A central mail hub (a mail server) receives e-mail for its users and the users on the client computers that it serves. Users either NFS-mount their incoming mail files to their local computers (the clients), or log in to the hub to read their mail.
• Disadvantages: • • each client can send and receive its own electronic mail. Therefore if the hub goes down or becomes overloaded, local mail traffic is unaffected (only mail to and from computers outside of the workgroup is affected). Greater privacy for electronic mail users on the client machines. Data is not stored in a central repository. Each computer needs to run its own copy of the sendmail daemon to “listen” for incoming mail.
Data Centralization By having your mail files on a single machine or directory structure, it is easier to back up your data. Company Appearance and Future Planning By using one of the topographies that use a hub computer, a small company can look more like a large corporation. As the company grows, the centralized mail processing can be easily moved to the jurisdiction of a corporate communications group.
1. On each client computer in the workgroup being served by a central mail hub, edit the file /etc/rc.config.d/mailservs: a. Set the environment variable SENDMAIL_SERVER to 0, indicating that this computer is not the hub, and is not a standalone e-mail system. The sendmail daemon will not be run on this computer: SENDMAIL_SERVER=0 b. Set the environment variable SENDMAIL_SERVER_NAME to the official host name of the hub computer that will send and receive electronic mail on behalf of this client computer.
outgoing e-mail from the entire workgroup, even mail sent from a system that has NFS mounted an electronic mailbox, appears to have originated on the hub computer. Configuring the Hub With Central Mail Hub topography, the electronic mail hub is the computer that receives e-mail from any computer outside of the workgroup on behalf of its own users and those of the client computers that it serves. 1. On the hub computer only, edit the file /etc/rc.config.d/mailservs: a.
Configuring the Hub The procedure for configuring the hub computer in a Gateway Mail Hub topography is: 1. On the hub computer, edit the file /etc/rc.config.d/mailservs: a. Set the environment variable SENDMAIL_SERVER to 1 to indicate that this computer is the hub computer: SENDMAIL_SERVER=1 b. Set the environment variable SENDMAIL_SERVER_NAME to null to indicate that no other computer serves this one: SENDMAIL_SERVER_NAME= c.
• Edit the /etc/rc.config.d/mailservs file: a. Set the SENDMAIL_SERVER environment variable to 1. Although you are configuring a client computer in the workgroup, setting this environment variable to 1 will start the sendmail daemon each time you boot your client computer so that it can receive e-mail from other systems in your workgroup. SENDMAIL_SERVER=1 b. Set the SENDMAIL_SERVER_NAME environment variable to the name of the computer that will be the gateway to the outside world.
Fully Distributed (Standalone System) Topography When using a Fully Distributed electronic mail topography, each computer is a standalone machine (with regard to electronic mail). Each machine is effectively its own workgroup and is configured just like the hub computer in a Central Mail Hub topography e-mail network. Configuring Each System The procedure for configuring each system in a Fully Distributed topography is: 1. Edit the file /etc/rc.config.d/mailservs: a.
8 Setting Up the Online Manpages There are three ways to set up online manpages, each resulting in a different amount of disk usage and having a different response time: 1. Fastest response to the man command (but heaviest disk space usage): Create a formatted version of all the manpages. This is a good method if you have enough disk space to hold the nroff originals and the formatted pages for the time it takes to finish formatting.
Regardless of how you set up the manpages, you can recover disk space by removing the nroff source files. CAUTION: Before removing any files, make a backup of the man directories you created in case you need to restore any files. For example, to remove files for section 1 in /usr/share/man, enter: # rm man1/* # rm man1.Z/* This concept for recovering disk space also applies to localized manpages. For further details, see man(1) and catman(1M).
9 Configuring Peripherals To add peripherals to your system, consult the following documentation: • • The hardware installation document that came with the peripheral. For PCI OL* information, see the Interface Card OL* Support Guide. For PCI OL* information on nPartition-able systems, see the nPartition Administrator's Guide. PCI OL*, previously known as OLAR, is the ability to add or remove a PCI card without needing to completely shutdown the entire system.
What is PCI Error Recovery? If PCI Error Recovery is enabled and an error occurs on a PCI bus containing an I/O card that supports PCI Error Recovery, the following steps are taken: 1. 2. The PCI bus is quarantined to isolate the system from further I/O and prevent the error from damaging the system. The PCI Error Recovery feature attempts to recover from the error and re-initialize the bus so I/O can resume.
pci_error_tolerance_time, the card in the I/O slot will be suspended and you will need to attempt a manual recovery operation to restore the card. PCI Error Recovery Documentation PCI Error Recovery is supported by the following documentation, available on the HP Technical Documentation web site at http://docs.hp.
# netstat -in 9. Assign IP addresses and subnet masks to additional cards as desired (options given later). See “Assigning IP Addresses and Subnet Masks to Additional Cards Using Web-Based HP SMH” (page 137). 10. For each interface, run ifconfig to verify the correct IP, netmask, and broadcast addresses. For example: # ifconfig lan0 11. For each interface, ping the broadcast address shown in Step 10 and verify that you get responses from other nodes on that subnet.
Assigning IP Addresses and Subnet Masks to Additional Cards Using Web-Based HP SMH To configure the LAN cards, you can use the web-based HP System Management Homepage (HP SMH). 1. 2. 3. 4. 5. 6. 7. 8. Ensure that an X Window System server is running on your local system. See “Using the X Window System” (page 32). Start web-based HP SMH from your local system. See “Starting an HP SMH Web Client” (page 24).
add IP addresses, and if desired, subnet masks, and any other optional settings. The 10 Gigabit Ethernet driver ixgbe is not pre-loaded; it is selectable. So, when setting up 10 Gigabit Ethernet networking for the first time on a system, you need to load it onto your hard drive using the swinstall utility. e. Where can I get the software? All of the currently used networking drivers are included in the latest quarterly HP-UX update. The drivers are also available on the web. Go to http://www.hp.
Class I H/W Path Driver S/W State H/W Type Description =================================================================== lan 6 1/0/2/1/0/6/0 iether CLAIMED INTERFACE HP AD193A PCI/PCI-X 2-port 4Gb FC/2-port 1000B-T Combo Adapter lan 6 1/0/2/1/0/6/1 iether CLAIMED INTERFACE HP AD193A PCI/PCI-X 2-port 4Gb FC/2-port 1000B-T Combo Adapter The last two digits of the hardware path (third column) reflect the path of each port; in the sample output shown, the 0 indicates LAN A and the 1 indicates LAN B (for the
communicating with systems outside the local network, the ROUTE_GATEWAY must be the IP address of the gateway router. The system maintains a dynamic routing table in memory. This routing table is dynamic information on how to route to a specific system or network. You can add and delete routes in this table by using the route command. You can force a specific path to a destination if there is more than one way to get there. For details, please see the route(1M) manpage.
2. Test the card and link with nwmgr, as follows: # nwmgr -c lanPPA -A link_state,speed For example, # nwmgr -c lan0 -A link_state,speed lan0 current values: Link State = Up Speed = 1 Gbps Full Duplex (Autonegotiation : On) The Speed line includes the current speed, the current duplex setting, and how the setting was determined. If the last item says Autonegotiation : On (as above), this indicates you have set the card to auto_on and the card determines the correct setting.
• Start web-based HP SMH as described in “Starting an HP SMH Web Client” (page 24). Then: 1. Navigate to Tools→ Network Interfaces Configuration→Network Interface Cards. 2. Select the NIC tab. 3. Select the LAN interface by clicking the radio button. The interface details are displayed below the list box. 4. In the right hand actions column, click View/Modify NIC Attributes. The View/Modify NIC Attributes window is displayed. 5.
Table 9-2 Choosing a Configuration Tool Associated system and networking Use tool or command tasks For further information If setting up first network access set_parms on a system, you will need an IP You can configure the first or address, and a host name. “core” LAN even if the configuration was postponed until after startup. See “Setting System and Network Parameters” (page 41) or set_parms(1M). If adding multiple LAN cards: To assign static IP addresses, use See “Assigning IP Addresses and HP SMH.
1. Make sure the file set NONHPTERM is on the system by using either of these methods: • # swlist -l fileset NonHP-Terminfo If the file set exists, the entry for NonHP-Terminfo.NONHPTERM will be displayed. • # ll /var/adm/sw/products/NonHP-Terminfo If the file set exists, the directory /var/adm/sw/products/ NonHP-Terminfo/NONHPTERM will exist. If the fileset is not on the system, you will need to load it from your latest HP-UX media.
4. Set the user’s TERM variable in the appropriate login script (either .profile for Korn and POSIX shell users or .login for C shell users in their home directory) to any of the names you uncovered in Step 2. For example: # export TERM=wy100 (Korn or POSIX shell) # setenv TERM wy100 (C shell) The default versions of these scripts prompt the user for the terminal type upon log in, so rather than editing the script, you could simply tell the user to respond with the terminal name.
1. Determine the status of the system. Is the system still up? If not, you’ve probably found your problem. You will need to reboot the system. Is the system in single user state? If so, the only active terminal will be the system console. Other terminals will not respond. You will need to switch to a multiuser state. See the init(1M) manpage for more information on changing run states.
If the problem is an application program that’s looping or not functioning properly, try pressing the Break key and then try the intr signal (usually Ctrl-C) or the quit signal (usually Ctrl-\) to see if you can get a shell prompt back.
7. Kill processes associated with the problem terminal. CAUTION: Use extreme caution when killing processes. The processes will be immediately and unconditionally terminated. Some valid processes might take a long time to complete. Be sure to type carefully when entering the PID numbers for the kill command to avoid killing the wrong process. If you have another terminal that is still working, go to that terminal and log in (you will need to be superuser).
If the file’s permissions are set to allow write access and the file isn’t displayed on the terminal, check the major and minor numbers of the device file. You can list them with the ll command. You can use the lssf command to interpret the major and minor numbers and display the results.
11. Other things to check. • Make sure your inittab entries are active If you are just adding this terminal and have made a new entry in the /etc/ inittab file by editing it, remember that this doesn’t automatically make your new entry active. To do that you need to enter the command: # init -q This tells the init process to scan the /etc/inittab file to update the information in its internal tables. • Check for functioning hardware. Now is the time to check the hardware.
terminal/cable combination works in its new location), then the problem is most likely with your MUX, port, or interface card. Other Terminal Problems The other type of problem you’re likely to run into with terminals is that of garbage on the screen. Garbage on the screen comes in two types: garbage intermixed with valid data characters and complete garbage.
10 Configuring the Kernel With each successive release of HP-UX, system administrators have increasing ability to make changes to the configuration of the HP-UX kernel without experiencing costly and inconvenient downtime. Innovations such as Dynamic Kernel Tunables and Dynamically Loadable Kernel Modules allow critical maintenance tasks to be performed without sacrificing application availability.
What Is a Kernel Configuration? Logically, a kernel configuration is a collection of all of the administrator choices and settings needed to determine the behavior and capabilities of the HP-UX kernel.
The kcpath command prints information about the location of the currently running kernel. It is intended for use by scripts and applications that need this information. See the kcpath(1M) manpage for details. The kclog command searches the kernel configuration log file. For details, see “The Kernel Configuration Log File” (page 195) or the kclog(1M) manpage. Finally, users of the mk_kernel command, present in previous HP-UX releases, should be aware that the command can still be used.
Figure 10-1 Sample Kernel Configuration Web Page Other Kernel Configuration Operations Other sections below describe some special kernel configuration operations and special uses of the kernel configuration commands. The usage of some kernel resources can be monitored, with alarms delivered when usage rises above a set threshold. These alarms can be configured and reviewed using the kcalarm command or the HP SMH tool. The resource usages can be reviewed using the kcusage command or HP SMH.
All kernel configuration changes made using the kernel configuration commands are logged to the file /var/adm/kc.log. Details about this log file can be found in “The Kernel Configuration Log File” (page 195), and the kconfig(5) and kclog(1M) manpages. The primary kernel configuration commands support a specialized output format that is designed for use by scripts and applications that need to parse the output of the commands.
Table 10-1 Common Kernel Configuration Command Line Options (continued) Option Description k c o n f i g k c m o d u l e k c t u n e -D (difference) Display only elements for which there is a change being held o for next boot. o o -h (hold) Hold the requested changes for next boot. o o o -P (parse) Use the special parsable output format. o o o -S (set) Display only elements that have been set to something other than default.
NOTE: This is a note. It provides information about how the operation completed, or other information of potential interest to the administrator. * This is a progress message. It displays the steps completed during the operation. Common Exit Status Codes All of the kernel configuration commands exit with one of the following status codes. 0 The operation was successful. 1 The requested changes could not be applied to the currently running system. They are being held and will be applied at next boot.
–n (next boot); when explicitly discarded using kconfig –H (unhold); or when subsequent changes are made that override them. For example, if you run. # kctune –h nproc=5000 # kctune nproc=6000 # set to 5000, hold for next boot # set to 6000, now the value of nproc at next boot will be 6000. The change to 5000 is discarded. A warning will be printed in these situations. Changes that are made to the currently running system are retained when the system is rebooted. They remain in effect until changed.
PCItoPCI autofs cachefs cifs rng vxportal wsio static static auto auto loaded static static depend best best explicit explicit explicit required auto-loadable, unloadable auto-loadable, unloadable loadable, unloadable auto-loadable, unloadable With the -d Option The -d option adds the description of each module.
The special keyword ALL displays all the possible categories. Compare with the -v option. # kcmodule -P ALL autofs cachefs name autofs desc Automounter File System version 1.0 timestamp Tue Sep 12 21:53:28 2006 [45078EC8] state static cause best next_state static next_cause best capable static unused depend module nfswrp:0.0.0 depend interface HPUX_11_31_PERF:1.0 name cachefs desc Cache File System version 1.
Each kernel module in the currently running configuration has a state, which describes how the module is being used. The possible states are: unused The module is installed on the system but not in use. static The module is statically bound into the kernel executable. This is the most common state. Moving a module into or out of this state requires relinking the kernel executable and rebooting. loaded The module is dynamically loaded into the kernel. Newer modules support this state.
TIP: To see if a module is required, look to see whether unused appears on the Capable line. If it does, the module is not required. Modules often have dependencies between them. For example, device drivers typically cannot be configured into the kernel unless the driver support modules are also configured. Dependencies like this are shown on the Depends On lines in the output. A module can be dependent on a particular other module, specified by name and version.
on the same kcmodule command line, or make the changes in a system file and import it. (See “Managing Configurations with System Files” (page 192).) Either of these techniques will ensure that the kernel executable is only relinked once. Sometimes you may want to force a change to be held for next boot, instead of applying it immediately. In these cases you can use the -h (hold) option with kcmodule to force that behavior.
Figure 10-2 Kernel Configuration Modules Tab Getting Information about Modules To get more detailed information about a particular module, do the following: • • Scroll to the module in the list. Click the radio button. The module details are displayed below the list, as shown in Figure 10-3.
Figure 10-3 Kernel Configuration Module Details Interpreting Module Information The module details block and the module list contain the information shown in Table 10-2.
Table 10-2 Kernel Module Details Fields (continued) Field Name Description Current Cause The reason why the module is in its current state (explicit, auto, depend, required, default) Next Boot State The state of the module after the system is restarted. Next Boot Cause The reason why the module is in its next boot state. Capabilities All the states that the module is capable of supporting.
Modify Kernel Module Figure 10-4 Modify Kernel Module The Modify Kernel Module display fields are described in Table 10-3.
Table 10-3 Modify Kernel Module Fields (continued) 3. Field Name Description Dynamic Whether the module is a dynamically loadable kernel module Dependencies All the modules on which this module depends This window also displays the areas that you can change, as shown in Table 10-4. The areas displayed depend on the capabilities of the module. Enter your changes. Table 10-4 Modify Kernel Module Change Options 4. 5. Field Name Description Next Boot State Choose the new state for the module.
Getting Information About Tunables When you run kctune with no options, it shows you the tunables associated with the kernel modules on your system (as well as any user-defined tunables), their current values, and the expressions used to compute those values. If there are changes to those values being held for next boot, those will be shown as well. On a typical system, the expression for most tunables is Default, meaning that the administrator is allowing the system to choose the tunable value.
Module Current Value Value at Next Boot Value at Last Boot Default Value Constraints Can Change Tunable Description Module Current Value Value at Next Boot Value at Last Boot Default Value Constraints Can Change Tunable Description Module Current Value Value at Next Boot Value at Last Boot Default Value Constraints Can Change pm_acct 4 [Default] 4 [Default] 4 4 acctresume >= -100 acctresume <= 101 acctresume > acctsuspend At Next Boot Only maxuprc Maximum number of processes for each non-root user pm_pro
constraint constraint constraint nproc >= semmnu + 4 nproc >= maxuprc + 5 nproc <= nkthread - 100 Use a comma-separated list with the -P option to display the categories you want. # kctune -P name,current maxuprc nproc name maxuprc current 256 name nproc current 4200 Interpreting Tunable Information Looking at the sample output above, you can see that each tunable has a name and a textual description.
thinks optimal, and to change it as needed. HP recommends that tunables be left set to default unless the default is known to be unsatisfactory. NOTE: Setting a tunable to Default is not the same thing as setting it explicitly to the default value reported by kctune. Using the example above, if you set nproc to 4200, its value will remain 4200 until you change it. However, if you set nproc to Default, its value will be kept up to date with any changes HP makes to the default value for nproc.
To create a user-defined tunable, use the -u (user-defined) option when you assign the tunable a value. The -u option is not needed to change the value of an existing user-defined tunable. Using the += symbol, you can increase the value of a tunable (by 100, in this example): # kctune nproc+=100 Using the >= symbol, you can ensure a minimum value of a tunable. The command: # kctune 'nproc>=5000' will set nproc to 5000 if its current value is below 5000.
You can view the tunables pane by selecting the Tunables tab on the HP SMH Kernel Configuration page, as shown in Figure 10-5. Figure 10-5 Kernel Configuration Tunables Tab Getting Information About Tunables To get more detailed information about a particular tunable, do the following: 1. 2. Scroll to the tunable in the list. Click the radio button. The tunable details are displayed under the list, as shown in Figure 10-6.
Figure 10-6 Kernel Configuration Tunable Details Interpreting Tunable Information The tunable details block and the tunable list contain the information shown in Table 10-5. Table 10-5 Tunable Details Fields Field Name Description Tunable The name of the tunable. Description A brief description of the tunable. Module The name of the module (if any) that the tunable is associated with. Tuning Capability Whether the tunable is Static, Dynamic, or Auto. Default The default value for the tunable.
Table 10-5 Tunable Details Fields (continued) Field Name Description Current Value The current maximum value for the resource. Next Boot Value The planned value, with all formulae computed. Next Boot Value (Expression) The formula (or integer) describing the next boot value. Range The range of values that are valid for the tunable. Constraints The dependencies that a tunable might have on other tunables as well as value restrictions.
Figure 10-7 Modify Kernel Tunable The Modify Kernel Tunable page displays the fields shown in Table 10-6. Table 10-6 Modify Kernel Tunable Fields Field Name Description Tunable Name The name of the tunable that will be modified. Description Description of the tunable. Module The kernel module that the tunable is associated with. Default The default value of the tunable. Range The range of acceptable values for the tunable. Negative numbers are indicated by a minus sign (-).
Table 10-6 Modify Kernel Tunable Fields (continued) 3. Field Name Description Current Value The current value of the tunable. Tuning Capability Displays whether the tunable is Static, Dynamic, or Auto. Current Usage The percentage of the resource that is being used. Constraints The dependencies that a tunable might have on other tunables and its value restrictions The Modify Kernel Tunable page also displays the areas that you can change, as shown in Table 10-7.
• • Find alarms that have been triggered View details on alarms You can view the alarms pane by selecting the Alarms tab on the HP SMH Kernel Configuration page, as shown in Figure 10-8. Figure 10-8 Kernel Configuration Alarms Tab Getting Information about Alarms To get more detailed information about a particular alarm, do the following: 1. 2. Scroll to the alarm in the list. Click the radio button to select it. The alarm details are displayed under the list, as shown in Figure 10-9.
Figure 10-9 Kernel Configuration Alarm Detail Interpreting Alarm Information The alarm details block and the alarms list contain the information shown in Table 10-8. Table 10-8 Kernel Configuration Alarm Fields 182 Field Name Description Tunable The name of the tunable. Description of Tunable The description of the tunable. Current Usage Value The percentage of resource being consumed at the previous polling. Event Type The event notification to be used.
Table 10-8 Kernel Configuration Alarm Fields (continued) Field Name Description Polling Interval The time interval between polling. Threshold The percentage at which the alarm should activate. Notification Type The notification method used when the alarm is triggered. The notification types are: console, email, opcmsg, snmp, syslog, textlog, tcp, and udp. See Table 10-10 for details. Notification Data Supplementary information used by the notification method.
Figure 10-10 Modify Kernel Alarm The Modify Kernel Alarm page displays the fields shown in Table 10-9. Table 10-9 Modify Alarm Fields Field Name Description Tunable The name of the tunable. Description of The description of the tunable. Tunable 184 Current Usage Value The percentage of resource being consumed at the previous polling. Event Type When notifications are to be sent: initial, repeat, return. See Table 10-10 for details.
Table 10-9 Modify Alarm Fields (continued) 3. Field Name Description Alarm Status The status of the alarm, one of the following: on The alarm is active. ringing The alarm has been triggered. off The alarm is deactivated. Polling Interval The interval, in minutes, between polling of resource usage. Notification Type The notification method: console, opcmsg, syslog, textlog, email, snmp, tcp, udp. Notification Data Supplementary information used by the notification method.
Table 10-10 Modify Alarm Change Options (continued) Field Name Description Notification Type Select the notification method to be used when the alarm is triggered. The choices are: console Send a message to the system console. Comment 4. 5. email Send an e-mail to the specified address. Fill in the Email Address field. opcmsg Send messages to ITO and OpenView applications via the opcmsg daemon. Select a value for Notification Data, one of normal, warning, minor, major, critical.
1. Click Add Alarm in the right-hand column of the Kernel Configuration Alarms window. The Add Alarm page is displayed, as shown in Figure 10-11. Figure 10-11 Add Alarm 2. In the dropdown list of the Tunable field, select the tunable you want to monitor. Note that only certain tunables are included in the list. If you select any, an alarm will be set on all the tunables in the list. You can set more than one alarm on any selectable tunable. 3. 4. 5.
2. At the bottom of the window, click one of the following buttons: • Activate to activate the alarm. The Alarm Status changes to on. • Deactivate to deactivate the alarm. The Alarm Status changes to off. • Remove to delete the alarm. The alarm is removed from the list. Resource Usage Commands The kcalarm command is used to add, delete, or list selected kernel tunable alarms, as well as turn kernel tunable monitoring on and off.
Managing Saved Configurations with kconfig When you have an HP-UX kernel configuration that satisfies your needs, you may want to save a copy of it to protect yourself against inadvertent configuration changes. Or, you may want to have multiple kernel configurations, so that you can switch between them easily. HP-UX allows you to save as many kernel configurations as you wish (subject to available disk space in /stand), and to modify them and use them at will.
State Capable Depends On unused static unused module OocCore:0.0.0 interface HPUX_11_31_PERF:1.0 ... Tunable Description Module Current Value Default Value NSTREVENT Maximum number of concurrent Streams bufcalls hpstreams 50 [Default] 50 ...
Each saved configuration can also have a title. The title can be used to provide yourself with a longer description of the configuration’s purpose or settings. It is optional. Each saved configuration also has a pair of timestamps. The Created/createtime stamp indicates when the configuration was created (kconfig –s). The Modify/modifytime stamp indicates when the configuration was last changed. Each timestamp is associated with the login name of the user who performed the action.
could be unpleasantly surprised at the effect of a pending change that had been forgotten. To find out which saved configuration is marked for use at next boot, use kconfig -w (which). This command also identifies the saved configuration that was most recently loaded or booted, or the system file that was most recently imported.
# kconfig –e filename • Export a saved configuration: # kconfig –e configname filename NOTE: /stand/system, and any system file created by exporting the running configuration, always reflects any changes that are being held for next boot. Once you have a system file, you can edit it using any text editor, making the changes you desire. After editing it, you can apply the changes with the kconfig -i (import) command.
Most changes made in system files can be made using the kernel configuration commands, and vice versa.
and import it there. This is an appropriate and effective way to ensure that two machines are running compatible configurations. (Compatible means they have the same set of kernel modules, but they may have different versions of those modules due to patch installations.) In some cases, running compatible configurations is not enough; you need to be sure that two machines are running exactly the same configuration.
Figure 10-12 View Change Log Parsing Command Output Improvements to HP-UX often require changes in the output formats of commands like those described here. This can be troublesome when applications or scripts have been written that parse the outputs of those commands.
applications. In addition to providing release-to-release compatibility, it is also easier to parse than human-readable output. CAUTION: HP reserves the right to change the other output formats of these commands at any time. HP will not support applications and scripts that parse the output of these commands unless they use the -P option. The -P option of each of these commands takes a list of field names, identifying the fields that the application wants to have appear in the output.
The Automatic Backup Configuration The system automatically maintains a saved configuration called backup. Generally, any time you use the kernel configuration tools to make a change to the currently running configuration, the previous (pre-change) configuration is saved to backup. Therefore the backup configuration is somewhat like the “undo” command in a word processor.
Integrity To boot a saved configuration on an Integrity system, interrupt the automatic boot process when it reaches the point that it has started the HP-UX boot loader. (On most systems, this is during the second 10-second countdown.) At the HPUX> prompt, type HPUX>boot thursday HP 9000 To boot a saved configuration on an HP 9000 system, interrupt the automatic boot process when you arrive at the boot console handler. Tell it to boot from the desired device (typically with a boot pri command).
When you boot the system in fail-safe mode, the previous kernel configuration will be automatically saved for you, with a configuration name something like saved_3DE78FA0. The exact name will be printed for you in the boot messages on the console. When you boot the system in fail-safe mode, the boot will stop when you reach single-user mode. At this time you should take any necessary steps to repair your system or your configuration and then reboot onto a valid configuration.
Guidelines for Recovering from Errors If you have an undesirable or unbootable kernel configuration, HP recommends the following approach to resolving the problem. • If your system is up: — If you know which configuration change caused the problem: ◦ If your backup configuration hasn’t been updated since the bad change: – Load the backup configuration with kconfig –l backup. ◦ Else (your backup configuration also has the problem in it): – Try to reverse the change using kcmodule or kctune.
The first thing Susan does is save a copy of the initial kernel configuration, in case she needs it later. She puts comments on all of her changes (with -C). She also puts a title on the saved configuration (with -t) to remind herself of what it contains. # kconfig -C "Save initial installation config" -s installed * The currently running configuration has been saved as ’installed’.
============== ========= ============== ======== ============== ========= lan0 UP 0x00306E4949FD gelan 1000Base-T Then she verifies that the modules are installed. # kcmodule -d gelan iether Module State Cause Notes Description gelan static best loadable, unloadable Gigabit Ethernet (gelan) LAN Driver iether static best loadable, unloadable Intel 8254X Ethernet Driver (for 100BT and Gigabit Cards) Finally, she removes the iether driver.
installed last_install Initial installation Created by last OS install # kconfig -w * The currently running configuration was created on Fri Dec 15 17:39:39 2006 by root as a copy of 'last_install'. * It was last saved on Fri Dec 15 17:45:11 2006 by root. * It was last modified on Fri Dec 15 18:04:58 2006 by root. Then, she saves the new kernel configuration under the name good, so that she can go back to it, if needed. She gives it a title to help recognize it later.
# kctune -C "Nightly billing s/w needs execute-on-stack" executable_stack=1 * The automatic 'backup' configuration has been updated. * The requested changes have been applied to the currently running configuration. Tunable Value Expression Changes executable_stack (before) 0 Default Immed (now) 1 1 The billing software also uses the kernel Random Number Generator module. Fred checks and sees that it’s not in use, but since it’s loadable he doesn’t need to reboot to use it.
running configuration. * The configuration 'day' has been loaded and is now in use. # kconfig -l night * The automatic 'backup' configuration has been updated. * The requested changes have been applied to the currently running configuration. * The configuration 'night' has been loaded and is now in use. When Susan returns from her vacation, the first thing she does is check the automatically maintained log file to see what Fred has done.
# kconfig -e night /tmp/system.night * The configuration 'night' has been exported to '/tmp/system.night'. Moving the file over to another machine, she imports the configuration there, using the -V option to ensure that exactly the same kernel software is in use. Then she loads the configuration. Something about the configuration can’t be changed immediately — probably a tunable setting — so she has to reboot the machine. As intended, the machine uses Fred’s night configuration when it comes back up.
Table 10-12 Working with System Files Procedure Command Create a system file... ...for a saved configuration kconfig -e configname filename ...for the currently running configuration 1 kconfig -e filename Create/update a configuration from a system file ... 2 ... create/update a saved configuration kconfig -i configname filename ...update the currently running configuration kconfig [-fhV] -i filename 1 2 Includes any changes being held for next boot. mk_kernel can also be used for this purpose.
Table 10-14 Working with Tunables (continued) Procedure Command ...apply change to saved configuration -c configname ...create user-defined tunable -u Table 10-15 Working with Kernel Modules Procedure Command List modules and their states... kcmodule [module]... ...verbose output -v ...only modules with changes held for next boot -D ...include required modules -a ...in a saved configuration -c configname Add a module to the configuration... ...in default state kcmodule module=best ...
Table 10-16 Working with the Kernel Configuration Log File (continued) Procedure Command ...counting only changes to a particular item -n modulename|tunablename|hwpath ...counting only log entries containing a string -f "string" Table 10-17 Kernel Configuration File Locations Procedure Command Saved configurations are stored in... /stand/configname Kernel executable is at... /stand/configname/vmunix System file is at... /stand/configname/system Currently running configuration is in...
Table 10-18 Kernel Configuration Methodology (continued) HP-UX 11i Version 1 and Before HP-UX 11i Version 2 and After Make configuration changes by editing /stand/ system and running config. Use mk_kernel instead. 1 Manage DLKMs with the kminstall, kmsystem, Manage DLKMs using kcmodule. 2 kmmodreg, kmadmin, kmupdate, and config commands. View or change tunables using kmtune. 4 1 2 3 4 Use kctune instead. 3 See “Managing Configurations with System Files” (page 192).
Table 10-19 Kernel Configuration Commands and Options (continued) HP-UX 11i Version 1 and Before HP-UX 11i Version 2 and After kmsystem -b No longer needed kmsystem -c y -l y modulename kcmodule modulename=loaded 2 kmsystem -c y -l n modulename kcmodule modulename=static 2 kmsystem -c n modulename kcmodule modulename=unused 2 kmsystem -q modulename kcmodule -v modulename 2 kmtune (no options) 3 kctune 4 kmtune -l 3 kctune -v 4 kmtune -q tunable 3 kctune tunable 4 kmtune -r tunable 3 kctun
Table 10-20 Kernel Configuration Files and Directories (continued) HP-UX 11i Version 1 and Before HP-UX 11i Version 2 and After Test kernel: /stand/build/vmunix_test (default output of mk_kernel) Test configuration: hpux_test 2 Primary system file: /stand/system /stand/system 2 Module system files: /stand/system.d/* No longer used. The data are now in the primary system file, /stand/system. 2 Master files: /usr/conf/master.d/* No longer used.
Index Symbols $HOME/.cshrc file, 42, 68 $HOME/.forward file, 54 $HOME/.kshrc file, 54 $HOME/.login file, 42, 68 $HOME/.profile file, 42, 68 $HOME/.rhosts file, 54 example, 72 /dev/ttyconf file, 37 /etc/csh.login file, 42, 68 /etc/default/autofs file, 80 /etc/default/security file, 36 /etc/dfs/dfstab file, 72, 84, 85 /etc/exports file, 75 /etc/fstab file, 80, 82, 84, 85 /etc/group file, 67, 88 /etc/hosts file, 84, 85 /etc/hosts.equiv file, 72 /etc/inetd.
JFS file system, 68 add a group HP SMH, text-based, 59 add a user command, 60 commands, 61 HP SMH, text-based, 50 with a template, 55 useradd command, 60 AUTOMOUNT_TIMEOUT environment variable, 80 C case studies user on multiple systems, 70 characters eof, 37 erase, 37 intr, 37 kill, 37 quit, 37 start, 37 stop, 37 CIFS sharing directories between HP-UX and Windows, 107 clients X Window System, 73 commands accept, 112, 114, 117 add a user, 60, 61 adding local printer to spooler, 112 adding network printer t
problems, 40 set_parms command, 40 setting, 40 setting with set_parms command, 42 delete a user HP SMH, text-based, 58 userdel command, 60 directories /etc/skel, 54 /homeroot, 47 home, 50 local, 70 remote, 70 case study, 70 skeleton, 54 DISPLAY environment variable, 30 DNS server setting with set_parms command, 42 domain name setting with set_parms command, 42 Domain Name Service (see DNS) E e-mail (see mail) electronic mail (see mail) environment variables, 11 (see also variables) AUTOMOUNT_TIMEOUT, 80 DI
configuring with HP SMH, text-based, 87 copy files between systems, 87 login /etc/inetd.
ACLs, 68 K kernel automatic backup, 198 booting in fail-safe mode, 199 booting saved configuration, 198 configuration command overview, 154 configuration commands common behavior, 157 configuration example, 201 configuration features, 153 configuration log file, 195 configuration purpose, 154 configuration with HP SMH, 155 error recovery, 197 error recovery guidelines, 201 kcmodule command, 160 managing configurations with system files, 192 managing running configuration with kconfig command, 188 managing
HP SMH, text-based, 57 usermod command, 60 mounting file systems, 70 multisystem access user ID, 69 multiuser mode, 38 N Network File System (see NFS) network gateway setting with set_parms command, 42 network parameters setting, 41 networking, 75 NFS /etc/dfs/dfstab file, 75 /usr/sbin/share command, 75 client enable or disable, 76 enable or disable with HP SMH, text-based, 76 clients, 75 configuring, 75 exporting vs sharing, 75 server enable or disable, 76 enable or disable with HP SMH, text-based, 76 sha
phone passwd field, 51 plotters (see printers) power failure recovery, 86 preloaded system starting, 35 primary group passwd field, 50 printers adding class to spooler, 117 adding local printer to spooler, 112 with commands, 112 with HP SMH, text-based, 112 adding local printer to system, 112 adding network printer to spooler, 116 with commands, 116 with HP SMH, web-based, 116 adding printer class to spooler with commands, 117 adding remote printer to spooler, 113 with commands, 114 with HP SMH, text-based,
starting, 111 commands, 112 HP SMH, text-based, 112 stopping, 111 commands, 112 HP SMH, text-based, 112 start character, 37 startup files $HOME/.kshrc, 54 /etc/skel/.cshrc, 54 /etc/skel/.exrc, 54 /etc/skel/.login, 54 /etc/skel/.
sharing directories between HP-UX and Windows, 106 sharing directories with CIFS (SMB), 107 Telnet from HP-UX to Windows, 108 from Windows to HP-UX, 109 X X Window System, 32 HP-UX client system, 32 non-HP-UX client system, 33 server access, 73 223
