Admin file solaris

I'm trying to do a pkgadd on Solaris with non-interactive. While reading the man page, I found out that i can disable interaction by using admin file. So i followed the guideline here. Google then lead me to this site. Since pkgadd can be done, I assume pkgrm should be the same as well. Then I thought maybe its just the same problem as pkgadd. Instead it gave me an error. What is it exactly that I should pass so that I can do pkgrm non-interactively.

Should i add another parameter inside the admin file? If so, what is the parameter? This is the parameter that I have tried using:. Found a hint here. The following shows deleting the user3 account:. Group accounts can be added, modified, or deleted using command-line utilities or by using the admintool 1M command. Use of the admintool command reduces or eliminates the possible introduction of typos and other errors that might affect all the group accounts. Both the admintool command and the command-line utilities are described in the following sections.

To create a group account, start the admintool command if it is not already active. Display the Groups window by selecting Groups from the Browse pull-down menu. Enter a unique group name in the Group Name field. In the Members List field, enter one or more user account names separated by commas. Using the mouse, click OK. The new group is displayed in the Groups window.

To modify a group account, display the Group window. Click the account you want to modify, and then select Modify from the Edit menu. Change the fields in the Modify Group window, and click Apply to save the changes.

To delete a group account, display the Groups window, and then select the account you want to delete. Select Delete from the Edit menu. A Warning window displays that lists the group.

Click Delete. Because using the admintool command makes creating, modifying, and deleting group accounts very easy and intuitive, Exam concentrates on using the groupadd , groupmod , and groupdel commands for administering group accounts. The groupadd 1M command provides a quick method to add a new group account. At a minimum, the group account name must be specified as a command-line argument.

The groupadd command supports two other command-line arguments. The first is -g gid , which used to specify the unique GID associated that should be associated with group. The other command-line argument is -o , which allows a duplicate GID to be assigned to the group. The groupmod 1M command is used to modify an existing group account. The command-line arguments are identical to the groupadd command-line arguments, except the new group account name is specified using -n name if the group account name is being modified.

The following example shows how to use the groupmod to change group newgroup to ngroup. The groupdel 1M command is used to delete a group account. The group account is specified as a command-line argument. Password administration involves setting parameters to control password aging, changing a user's password as needed, and possibly locking a user account to prevent use. This includes how long a password is valid Max Change , how often it can be changed Min Change , and how long an account can be inactive before the password must be changed Max Inactive.

These parameters enforce a policy for protecting the integrity of passwords. Note that of these three password-aging parameters, only Max Inactive can be specified using the useradd command and modified using the usermod command.

Unless specified by a superuser account such as root , passwords must meet the following requirements:. The default is six. It is best to increase this value to eight. A password cannot be the same as user account name, the reverse of the user account name, or a circular shift of the user account name.

Any uppercase letters are mapped to lowercase letters for requirement checking. This means that the password for the guest user account cannot be guest, tseug, uestg, estgu, GUEST, and so on. Once again, uppercase and lowercase letters are equivalent for requirement checking. Passwords can be any length, but only the first eight characters are significant.

For example, a password can be defined as 25administration but 25admini is actually used to log into the system. Keep in mind that these requirements do not apply when root or some other superuser account defines its own password or the password of another user account. To change the password of a user account, start the admintool command if it is not already active. The user account can be selected in two ways: by double-clicking the account entry or by clicking the account entry to highlight it and then selecting Modify from the Edit pull-down menu.

Using either method, the Modify User window is displayed. To modify the account password, position the mouse cursor over the Password field and hold down the left button. Then, move the mouse cursor over the Normal Password item and release the mouse button. Enter the same password for both the Enter Password and the Verify Password fields.

Asterisks are displayed in place of each character entered. To save the password, click OK in the Modify User window. Other than using the admintool command, the passwd 1 command is the only other way to change the password for a user account.

When used without any command-line arguments, the passwd command changes the password of the current user account. The following code shows how to change the password for the currently logged in user dla :.

Note that the current password must be entered before a new password can be specified. When a superuser account, such as root, uses the passwd command, the current password is not required. A variety of command-line arguments are provided to support changing passwords. So, if we check the file3 in dir1 after the example above, we can see that even though dir1 now belongs to user nobody, file3 in it still belongs to me:.

If your intention is to change ownership of all the files and directories of a certain location in your filesystem, you need to use a -R option of the chown command, which means recursive ownership change:.

Now, if I create a new file, it will by default belong to my primary group called greys, just like my username :. Mail Services Reference. Part V Serial Networking Topics. Solaris PPP 4. Working With Remote Systems Overview. Accessing Remote Systems Tasks. Monitoring Network Performance Tasks. Mail aliases must be unique within the domain. This section provides the procedures for administering mail alias files. In addition, you can create database files for the local mail host by using makemap.

Refer to the makemap 1M man page. The use of these database files does not provide all of the advantages of using a name service such as NIS. However, you should be able to retrieve the data from these local database files faster because no network lookups are involved.

Use the following procedure to facilitate aliasing with an NIS mail. The changes are active in only a few minutes, at most. Use the following procedure to resolve aliases with a local mail alias file. You can copy the three files by using the rcp or rsync commands. Refer to the rcp 1 man page or the rsync 1 man page for more information. Alternately, you can create a script for this purpose.

When you copy these files, you do not need to run the newaliases command on each of the other systems. You can copy these files by using the rcp or rsync commands. The first entry redirects mail to a new alias. The next entry creates a message when an incorrect alias is used.