IBM AIX Version 7.1 文件参考指南

需积分: 10 144 浏览量更新于2024-07-16 收藏 6.12MB PDF 举报

"AIX7.1_file_reference.pdf" 本资源是IBM公司针对AIX操作系统版本7.1的文件参考指南，适用于从2010年至2016年以及之后的所有更新和修改，除非在新的版本中有特别说明。该文档主要面向AIX Version 7.1的用户，旨在提供关于系统文件、配置文件、管理文件等的详细信息。在文档中，读者需要注意的是，内容的使用、复制或披露受到美国政府用户的特定限制，这些限制遵循GSA ADP日程合同的规定，由IBM公司授权。文档的设计符合ISO9000标准，确保了质量管理和控制。 "Files Reference"部分是文档的核心，涵盖了AIX 7.1系统中的各种关键文件。以下是一些重要的文件介绍： 1. **access_lists File**：这个文件与访问控制列表相关，可能包含了对系统资源访问权限的设置，用于管理用户或组的访问权限。 2. **acct.cfg File**：这是会计配置文件，用于定义系统如何记录和管理用户的资源使用情况，如CPU时间、磁盘空间等。 3. **admin File**：通常涉及系统管理相关的配置，可能包含管理员级别的设定和命令。 4. **aliases File for Mail**：邮件别名文件，用于定义电子邮件地址的别名，使得邮件可以被正确地转发到相应的收件人。 5. **audit File for BNU**：BNU（Berkeley Network Utilities）的审计文件，用于记录网络服务的活动，提供安全监控和审计跟踪。 6. **/etc/security/authorizations File**：这是一个重要的安全文件，定义了用户或组可以执行的特定操作或系统功能的授权。 7. **autosecrets File**：自动秘密文件，可能包含自动化的密码管理和加密密钥，确保系统的安全性。这些文件在AIX系统中扮演着关键角色，它们的配置和管理对于系统的稳定运行和安全性至关重要。通过理解并正确使用这些文件，系统管理员可以更好地维护和优化AIX环境。文档的其余部分将深入到更多文件的详细信息，包括它们的用途、格式和配置方法，是AIX管理员必备的参考资料。

Eleven parameters can be defined in an admin file. A file is not required to assign values to all eleven

parameters. If a value is not assigned, pkgadd asks the installer how to proceed.

The eleven parameters and their possible values are shown below except as noted. They may be specified

in any order. Any of these parameters can be assigned the value ask, which means that, if the situation

occurs, the installer is notified and asked to supply instructions at that time.

Parameter Description

basedir Indicates the base directory where relocatable packages are to be installed. The value may contain $PKGINST to

indicate a base directory that is to be a function of the package instance.

mail Defines a list of users to whom mail should be sent following installation of a package. If the list is empty or if

the parameter is not present in the admin file, the default value of root is used. The ask value cannot be used

with this parameter.

runlevel Indicates resolution if the run level (system state) is not correct for the installation or removal of a package.

Options are:

nocheck Do not check for run level (system state).

quit Abort installation if run level (system state) is not met.

conflict Specifies what to do if an installation expects to overwrite a previously installed file, thus creating a conflict

between packages. Options are:

nocheck Do not check for conflict; files in conflict are overwritten.

quit Abort installation if conflict is detected.

nochange

Override installation of conflicting files; conflicting files are not installed.

setuid Checks for executables that have setuid or setgid bits enabled after installation. Options are:

nocheck Do not check for setuid executables.

quit Abort installation if setuid processes are detected.

nochange

Override installation of setuid processes; processes are installed without setuid bits enabled.

action Determines if action scripts provided by package developers contain possible security impact. Options are:

nocheck Ignore security impact of action scripts.

quit Abort installation if action scripts may have a negative security impact.

partial Checks to see if a version of the package is already partially installed on the system. Options are:

nocheck Do not check for a partially installed package.

quit Abort installation if a partially installed package exists.

idepend Controls resolution if other packages depend on the one to be installed. Options are:

nocheck Do not check package dependencies.

quit Abort installation if package dependencies are not met.

rdepend Controls resolution if other packages depend on the one to be removed. Options are:

nocheck Do not check package dependencies.

quit Abort removal if package dependencies are not met.

space Controls resolution if disk space requirements for package are not met. Options are:

nocheck Do not check space requirements (installation fails if it runs out of space).

quit Abort installation if space requirements are not met.

The value ask cannot be defined in an admin file that is used for non-interactive installation (since by

definition, there is no installer interaction). Doing so causes installation to fail when input is needed.

Related reference:

“depend File” on page 72

“pkginfo File” on page 217

Related information:

6 AIX Version 7.1: Files Reference

pkgadd command

aliases File for Mail

Purpose

Contains alias definitions for the sendmail command.

Description

The /etc/mail/aliases file contains the required aliases for the sendmail command. Do not change these

defaults, as they are required by the system. The file is formatted as a series of lines in the form:

name: name_1, name_2, name_3,...

The name: is the name of the alias, and the name_n are the aliases for that name. Lines beginning with

white space are continuation lines. Lines beginning with a # (pound sign) are comments.

Aliasing occurs only on local names. System-wide aliases are used to redirect mail. For example, if you

receive mail at three different systems, you can use the /etc/mail/aliases file to redirect your mail to one

of the systems. As an individual user, you can also specify aliases in your .mailrc file.

Aliases can be defined to send mail to a distribution list. For example, you can send mail to all of the

members of a project by sending mail to a single name.

The sender of a message is not included when the sendmail command expands an alias address. For

example, if amy sends a message to alias D998 and she is defined as a member of that alias, the sendmail

command does not send a copy of the message to amy.

The /etc/mail/aliases file is a raw data file. The sendmail command uses a database version of this file.

You must build a new alias database by running the sendmail -bi command or the newaliases command

before any changes made to the /etc/mail/aliases file become effective.

As long as you do not rebuild the aliases database, sendmail will continue to read it in its old DBM

format. This consists of two files: /etc/mail/aliases.dir and /etc/mail/aliases.pag. However, the moment

you rebuild the aliases database, sendmail will change this format to Berkeley DB. This file will be stored

in /etc/mail/aliases.db.

Note: Upper case characters on the left hand side of the alias are converted to lowercase before being

stored in the aliases database. In the following example, mail sent to the testalias user alias fails, since

TEST is converted to test when the second line is stored.

TEST: user@machine

testalias: TEST

To preserve uppercase in user names and alias names, add the u flag to the local mailer description in the

/etc/mail/sendmail.cf file. Thus, in the example above, mail to the testalias user alias would succeed.

Files

Files Reference 7

Item Description

/etc/mail/aliases Contains systemwide aliases.

/etc/mail/aliasesDB directory Contains the binary files created by the newaliases command, including the

DB.dir and DB.pag files.

/etc/mail/aliases.db Contains the binary file storing the aliases database in Berkeley DB format,

created by the newaliases command

Related reference:

“.mailrc File Format” on page 521

Related information:

newaliases command

sendmail command

Alias database building

audit File for BNU

Purpose

Contains debug messages from the uucico daemon.

Description

The /var/spool/uucp/.Admin/audit file contains debug messages from the uucico daemon when it is

invoked as a result of a call from another system. If the uucico daemon is invoked from the local system,

the debug messages are sent to either the /var/spool/uucp/.Admin/errors file or to standard output.

Files

Item Description

/var/spool/uucp/.Admin/audit Specifies the path of the audit file.

/var/spool/uucp/.Admin/errors Contains a record of uucico daemon errors.

Related information:

uudemon.cleanu command

cron command

BNU log files

BNU File and Directory Structure

/etc/security/authorizations File

Purpose

Contains the list of valid, user-defined authorizations.

Description

The /etc/security/authorizations file stores the list of valid, user-defined authorizations available on a

system. An authorization administrator can modify user-defined authorizations. System-defined

authorizations do not appear in this file. You can add new authorizations to this file using the mkauth

command and modify authorizations using the chauth command.

The /etc/security/authorizations file is an ASCII file that uses a stanza for each user-defined

authorization. Each stanza is identified by the authorization name followed by a colon (:). You can list

authorization attributes individually as Attribute=Value pairs on subsequent lines. Each attribute pair ends

with a newline character, as does each stanza. For an example of a stanza, see “Examples” on page 9.

8 AIX Version 7.1: Files Reference

When the system is operating in Enhanced RBAC Mode, changes that you make to the authorizations file

do not impact security considerations until you send the entire authorization database to the Kernel

Security Tables using the setkst command, or until the system is rebooted.

Modifying and listing entries in the authorizations file

Do not directly edit the /etc/security/authorizations file. Use the following commands and subroutines to

manipulate the authorization database:

mkauth

Adds new authorizations to the /etc/security/authorizations file.

chauth

Changes user-defined authorization attributes.

lsauth Displays authorizations that are defined in this file and system-defined authorizations.

rmauth

Removes entries from this file.

To write programs that affect entries in the /etc/security/authorizations file, use one or more of the

following subroutines:

v getauthattr

v getauthattrs

v putauthattr

v putauthattrs

Attributes

A stanza in this file contains one or more of the following attributes:

Attribute Description

id Specifies the unique numeric ID of the authorization. This is a required attribute and is used

internally for security decisions. Do not modify this ID after creating the authorization. The value

is a unique decimal integer greater than 10000. Values below 10000 are reserved for system-defined

authorizations.

dfltmsg Specifies the default authorization-description text if message catalogs are not in use. The value is

a character string.

msgcat Specifies the file name of the message catalog that contains the one-line description of the

authorization. The value is a character string.

msgset Specifies the message set that contains the authorization description in the message catalog. The

value is a decimal integer.

msgnum Specifies the message ID that contains the authorization description in the message catalog. The

value is a decimal integer.

Security

The root user and the security group own this file. This files grants read and write access to the root user.

Access for other users and groups depends on the security policy for the system.

Examples

The following example for the custom authorization displays a typical stanza in the file:

Files Reference 9

剩余1077页未读，继续阅读

casainurbania

粉丝: 22
资源: 4

IBM AIX Version 7.1 文件参考指南

Oracle Database 19c WINDOWS.X64_193000_db_home.zip.txt

AIX Version 7.1

IBM AIX 7.1 中文产品介绍

AIX6.1_file_reference.pdf

AIX_6.1_7.1_度盘.txt

aix7.1操作系统和设备管理.pdf

AIX.rar_AIX CHM_AIX unix c++_aix_aix c_aix.chm

aix7.1上安装oracle11g.doc

AIX7.1安装Sybase ASE 16.0 SP02.docx

R_TLQCli8.1.3.0_AIX5.3_64.tar.Z

最新资源