In this chapter, we have examined the basic procedures for managing users and groups on a Solaris system. Since all processes and threads are executed with a real or effective user and group ID, it’s important for administrators to understand how to manage these entities effectively.
1. |
What are the typical uses for a Solaris user account (choose two only)?
|
|
2. |
Which of the following groups contains only default system accounts?
|
|
3. |
What are the names of the two password files used by Solaris?
|
|
4. |
Which of the following users has a default UID of 0?
|
|
5. |
Which of the following useradd commands is valid?
|
|
6. |
Which of the following usermod commands would change the UID of the www account from 1004 to 1005?
|
|
7. |
A locked account can be identified in /etc/passwd by which of the following entries?
|
|
8. |
Which of the following userdel commands would delete account melissa (UID 1002)?
|
|
9. |
Which of the following groupadd commands is valid?
|
|
10. |
Which of the following characteristics cannot explicitly be set using admintool?
|
|
Answers
1. |
A or D. Most users log in with a shell and use it to launch applications. |
2. |
C. www, samba, and oracle are common accounts on Solaris, but they are user-installed. |
3. |
D. The passwd file doesn’t contain passwords anymore, but retains all user details. |
4. |
B. The root user has a default UID of 0, but this can be modified. |
5. |
C. UIDs and GIDs must be numeric. |
6. |
A. Only the UID needs to be identified with the –u parameter. |
7. |
C. *LK* indicates a locked account. |
8. |
D. UIDs must be used when deleting accounts. |
9. |
A. UIDs must be used when adding groups. |
10. |
D. admintool can be used to set the primary group, login shell, and an expiry date, but cannot perform normal shell tasks. |