| Skip Navigation Links | |
| Exit Print View | |
|
System Administration Guide: Naming and Directory Services (NIS+) |
| Skip Navigation Links | |
| Exit Print View | |
|
|
System Administration Guide: Naming and Directory Services (NIS+) |
Part I About Naming and Directory Services
Part II NIS+ Setup and Configuration
4. Configuring NIS+ With Scripts
5. Setting Up the NIS+ Root Domain
8. Configuring an NIS+ Non-Root Domain
10. NIS+ Tables and Information
12. Administering NIS+ Credentials
14. Administering Enhanced NIS+ Security Credentials
15. Administering NIS+ Access Rights
16. Administering NIS+ Passwords
18. Administering NIS+ Directories
Using the nistbladm Command With NIS+ Tables
nistbladm and NIS+ Column Values
nistbladm, Searchable NIS+ Columns, Keys, and Column Values
nistbladm and Indexed NIS+ Names
Creating Additional NIS+ Automount Tables
Adding Entries to an NIS+ Table
Adding an NIS+ Table Entry With the -a Option
Adding an NIS+ Table Entry With the -A Option
Editing an NIS+ Table Entry With the -e Option
Editing an NIS+ Table Entry With the -E Option
Removing NIS+ Single Table Entries
Removing Multiple Entries From an NIS+ Table
Displaying the Contents of an NIS+ Table
Displaying the Object Properties of an NIS+ Table or Entry
About Regular Expressions in NIS+
nismatch and nisgrep Command Syntax
Searching the First Column in NIS+
Searching a Particular Column in NIS+
Searching Multiple Columns in NIS+
Loading Information Into NIS+ From a File
Loading Data From an NIS Map Into NIS+
Dumping the Contents of an NIS+ Table to a File
20. NIS+ Server Use Customization
23. Information in NIS+ Tables
Common NIS+ Namespace Error Messages
The nissetup command expands an existing NIS+ directory object into a domain by creating the org_dir and groups_dir directories, and a full set of NIS+ tables. It does not, however, populate the tables with data. For that, you will need the nisaddent command, described in nisaddent Command. Expanding a directory into a domain is part of the process of setting up a domain.
Note - When setting up a new NIS+ domain, the nisserverscript is easier to use than the nissetup command. See Setting Up NIS+ Root Servers for a full description of using nisserver.
The nissetup command can expand a directory into a domain that supports NIS clients as well.
To use nissetup, you must have modify rights to the directory under which you'll store the tables.
You can use the nissetup command with or without a directory name. If you don't supply the directory name, it uses the default directory. Each object that is added is listed in the output.
rootmaster# /usr/lib/nis/nissetup doc.com. org_dir.doc.com. created groups_dir.doc.com. created auto_master.org_dir.doc.com. created auto_home.org_dir.doc.com. created bootparams.org_dir.doc.com. created cred.org_dir.doc.com. created ethers.org_dir.doc.com. created group.org_dir.doc.com. created hosts.org_dir.doc.com. created mail_aliases.org_dir.doc.com. created sendmailvars.org_dir.doc.com. created netmasks.org_dir.doc.com. created netgroup.org_dir.doc.com. created networks.org_dir.doc.com. created passwd.org_dir.doc.com. created protocols.org_dir.doc.com. created rpc.org_dir.doc.com. created services.org_dir.doc.com. created timezone.org_dir.doc.com. created
To expand a directory into a domain that supports NIS+ and NIS client requests, use the -Y flag. The tables are created with read rights for the nobody class so that NIS clients requests can access them.
rootmaster# /usr/lib/nis/nissetup -Y Test.doc.com.
|