Examining the Group File
The passwd_import command first checks the group file for name and then UNIX ID conflicts. When you resolve the conflict by answering the prompt, passwd_import creates the groups in the registry if it is so directed.
The following steps show how UNIX ID group conflicts are handled:
1. The passwd_import command first finds a conflict between UNIX IDs, as shown in the preceding topics. The name wheel in the group file and the name system in the registry both have UNIX IDs of 0. The passwd_import command prompts you for how to resolve the conflict, as follows:
CONFLICT: (wheel 0) - Import Group's UNIX id exists in registry.
(dce / sad)
(system 0) is the conflicting entry from the registry.
Do you wish to resolve the conflict (y) or skip this entry (n):
2. If you enter an n to skip the entry, passwd_import continues processing. If you enter a y to resolve the conflict, passwd_import prompts you for how to resolve the conflict. In the following example, the conflict is resolved by creating an alias of wheel for the system entry in the registry:
Do you wish to resolve the conflict (y) or skip this entry (n): y
Select one of: (a)lias, (g)enerate, (e)nter, (s)kip entry, (h)elp: a
>> Adding Group entry for: wheel 0
Because it is running in verbose mode, passwd_import describes the actions it is taking. Each action description is prefaced with the >> (redirection symbols).
If you are running passwd_import in check mode, you are not prompted to resolve the conflict. Instead, you are informed of the conflict and processing continues. The message looks like the following display:
CONFLICT: (wheel 0) - Import Group's UNIX id exists in registry.
(dce / sad)
(system 0) is the conflicting entry from the registry.
Would need new UNIX id to resolve conflict. (dce / sad)
3. If passwd_import does not find conflicts that you must resolve, it displays the group entries as it processes them and, because it is running in verbose mode, the actions it is taking. In the following example, you are not prompted to resolve the name conflict because passwd_import was invoked with the -i option.
CONFLICT: (tgroup 35)
- Group name exists in registry and UNIX ids match.
(dce / sad)
>> Import Group: - Ignoring name conflict, as instructed
(dce / sad)
>> Adding Group entry for: diags 48
>> Adding Group entry for: cheetah 50
>> Adding Group entry for: mkt_dev 52
As passwd_import continues through the UNIX group file, it finds two other UNIX ID conflicts: UNIX entries adm 4 and rje 8, which are in conflict with registry entries locksmith 4 and server 8, respectively.