Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Basic Administration Oracle Solaris 10 8/11 Information Library |
1. Oracle Solaris Management Tools (Road Map)
2. Working With the Solaris Management Console (Tasks)
3. Working With the Oracle Java Web Console (Tasks)
4. Managing User Accounts and Groups (Overview)
What's New or Changed in Managing Users and Groups?
Tools for User Account and Group Account Management
What Are User Accounts and Groups?
Using Large User IDs and Group IDs
Guidelines for Using User Names, User IDs, and Group IDs
Tools for Managing User Accounts and Groups
Tasks for Solaris User and Group Management Tools
Managing Users and Resources With Projects
Customizing a User's Work Environment
Using Site Initialization Files
Avoiding Local System References
Default File Permissions (umask)
User and Site Initialization Files Examples
5. Managing User Accounts and Groups (Tasks)
6. Managing Client-Server Support (Overview)
7. Managing Diskless Clients (Tasks)
8. Introduction to Shutting Down and Booting a System
9. Shutting Down and Booting a System (Overview)
10. Shutting Down a System (Tasks)
11. Modifying Oracle Solaris Boot Behavior (Tasks)
12. Booting an Oracle Solaris System (Tasks)
13. Managing the Oracle Solaris Boot Archives (Tasks)
14. Troubleshooting Booting an Oracle Solaris System (Tasks)
15. x86: GRUB Based Booting (Reference)
16. x86: Booting a System That Does Not Implement GRUB (Tasks)
17. Working With the Oracle Solaris Auto Registration regadm Command (Tasks)
18. Managing Services (Overview)
20. Managing Software (Overview)
21. Managing Software With Oracle Solaris System Administration Tools (Tasks)
22. Managing Software by Using Oracle Solaris Package Commands (Tasks)
Depending on your site policy, user account and group information can be stored in your local system's /etc files or in a name or directory service as follows:
The NIS+ name service information is stored in tables.
The NIS name service information is stored in maps.
The LDAP directory service information is stored in indexed database files.
Note - To avoid confusion, the location of the user account and group information is generically referred to as a file rather than as a database, table, or map.
Most user account information is stored in the passwd file. Password information is stored as follows:
In the passwd file when you are using NIS or NIS+
In the /etc/shadow file when you are using /etc files
In the people container when you are using LDAP
Password aging is available when you are using NIS+ or LDAP, but not NIS.
Group information is stored in the group file for NIS, NIS+, and files. For LDAP, group information is stored in the group container.
The fields in the passwd file are separated by colons and contain the following information:
username:password:uid:gid:comment:home-directory:login-shell
For example:
kryten:x:101:100:Kryten Series 4000 Mechanoid:/export/home/kryten:/bin/csh
For a complete description of the fields in the passwd file, see the passwd(1) man page.
The default passwd file contains entries for standard daemons. Daemons are processes that are usually started at boot time to perform some system-wide task, such as printing, network administration, or port monitoring.
root:x:0:0:Super-User:/:/sbin/sh daemon:x:1:1::/: bin:x:2:2::/usr/bin: sys:x:3:3::/: adm:x:4:4:Admin:/var/adm: lp:x:71:8:Line Printer Admin:/usr/spool/lp: uucp:x:5:5:uucp Admin:/usr/lib/uucp: nuucp:x:9:9:uucp Admin:/var/spool/uucppublic:/usr/lib/uucp/uucico smmsp:x:25:25:SendMail Message Submission Program:/: listen:x:37:4:Network Admin:/usr/net/nls: gdm:x:50:50:GDM Reserved UID:/: webservd:x:80:80:WebServer Reserved UID:/: postgres:x:90:90:PostgreSQL Reserved UID:/:/usr/bin/pfksh svctag:x:95:12:Service Tag UID:/: nobody:x:60001:60001:NFS Anonymous Access User:/: noaccess:x:60002:60002:No Access User:/: nobody4:x:65534:65534:SunOS 4.x NFS Anonymous Access User:/:
Table 4-6 Default passwd File Entries
|
The fields in the shadow file are separated by colons and contain the following information:
username:password:lastchg:min:max:warn:inactive:expire
For example:
rimmer:86Kg/MNT/dGu.:8882:0::5:20:8978
For a complete description of the fields in the shadow file, see the shadow(4) and crypt(1) man pages.
The fields in the group file are separated by colons and contain the following information:
group-name:group-password:gid:user-list
For example:
bin::2:root,bin,daemon
For a complete description of the fields in the group file, see the group(4) man page.
The default group file contains the following system groups that support some system-wide task, such as printing, network administration, or electronic mail. Many of these groups having corresponding entries in the passwd file.
root::0: other::1:root bin::2:root,daemon sys::3:root,bin,adm adm::4:root,daemon uucp::5:root mail::6:root tty::7:root,adm lp::8:root,adm nuucp::9:root staff::10: daemon::12:root sysadmin::14: smmsp::25: gdm::50: webservd::80: postgres::90: nobody::60001: noaccess::60002: nogroup::65534:
Table 4-7 Default group File Entries
|