Chapter 7, Configuring the Network Information Service (NIS)
The old master server must be running NIS to complete this procedure. This is because nonmaster servers consult their own copies of maps, which include the name of the old master server, when they receive a map transfer request originating from yppush on the master. New maps with the new master server listing must come from the old master server for the maps to be incorporated on slave and copy-only servers. Therefore, if the old master is not available when you change master servers, you must rebuild your entire NIS system from scratch. CAUTION: Changing master servers is a major reconfiguration of your network and should not be undertaken unless absolutely necessary. Make sure you understand the procedure thoroughly and back up your network configuration files before you begin. The procedures described here assume that the new master is running SCO NIS. Other implementations of NIS configure servers in a different way; consult the documentation for your version of NIS before changing master servers. To change NIS master servers, follow these steps:
\:
MAPS=`oawk '{print $1 ; }' /etc/yp/YP_MAP_X_LATE`
for map in $MAPS; do
echo moving $map
ypxfr -h new_master -f $map
yppush $map
done
Make sure your /etc/yp/YP_MAP_X_LATE file is current
before running this command; for more information, refer to
``NIS maps''.
See also:
|
Networking
guide Call : 800-519- 2267
Vibrant boot camp offers MCSE, CCNA, CCNP Certification back to back
Vibrant
offers
MCSE
certification
training
boot camp
for $5400
all inclusive,
instructor
led at
California
and
Baltimore.
|
Preboot Sequence, Process Accounting, Publishing Resources, Publishing Software Packages, Redeploying Software, Refreshing Group Policy at Established Intervals, Remote Assistance, Remote Desktop for Administration, Removing a Service Pack or Hotfix, Removing or Disabling Software, Requesting Assistance, Reroute Requests with Redirects, Resolving Conflicts Between Group Policy Settings, Restoring Active Directory Directory Services, Restoring Files and Folders, Roaming User Profiles, Security, Setting Up and Managing Published Printers, Setting Up and Managing Published Shared Folders, Setting Up Auditing, Shared Folder Permissions, Slipstreaming Service Packs and Hotfixes, Software Deployment, Software Installation and Maintenance Technology, Software Update Services, Support_388945a0 account credentials instead of the users credentials to perform specific administrative, System Requirements, TABLE OF CONTENTS : Installing and Deploying Windows Server 2003, Taking Ownership, Terminal Server Role, Terminal Services Components, Terminal Services, The Boot.ini File, The Deny Permission, The File Signature Verification Utility, The Logman Utility, MCSE Boot Camp Training get MCSE join MCSE Bootcamp, The Recovery Console, The relog Utility, MCSE Boot Camp Training get MCSE join MCSE Bootcamp, The Remote Desktop Connection Utility, The Remote Desktops Snap-In, The Session Manager, The Shutdown Event Tracker, The System Monitor, The typeperf Utility, The Windows Server 2003 Boot Process, Troubleshooting NTFS Permission Problems, Troubleshooting Terminal Services, Unattended Installation, Upgrading Software, Using a Saved File to Request Assistance, Using an Audit Policy, Using an Unattended Answer File, Using Configure Your Server Wizard and Add or Remove Programs to Install IIS, Using Driver Signing, Using E-Mail to Request Assistance, Using Event Viewer to View Security Logs, Using Event Viewer, Using Group Policy, Using Remote Installation Services, Using Scripting to Manage Website Content, Using Task Manager to Monitor Performance, Using the Recovery Console, Using the System Preparation Tool, Using User Profiles, Using Windows Messenger to Request Assistance, Viewing Security Logs, Virtual Directories, Volume Mounting, Web-Based Administration, Windows Server 2003 Licensing, Windows Server 2003 network, Windows Update Catalog, Windows Update