AIX 7.1文件参考手册更新及系统关键内容概览

需积分: 9 112 浏览量更新于2024-07-20 收藏 4.55MB PDF 举报

本文档是关于AIX Version 7.1的详细文件参考指南，它为用户提供了对操作系统内各类系统文件的深入理解，以及新版本中可能有的新增功能。AIX 7.1是一个高度稳定和功能强大的UNIX操作系统，适用于企业级环境，特别强调了安全性、性能优化和可管理性。文档首先要求用户在使用前阅读"Notes"部分（第1073页），了解可能的限制、适用范围以及版权信息。IBM Corporation在2010年和2013年对此版本拥有版权，并提醒美国政府用户，根据GSA ADP Schedule合同，使用、复制或披露受限。 "About this document"章节介绍了文档的目的和结构，确保读者能快速定位所需信息。接下来的章节详细阐述了： 1. **What's new in Files Reference**：这部分概述了AIX 7.1相较于前版的新特性，可能涉及文件系统的改进、新的配置选项和增强的安全特性。 2. **System Files**：这部分涵盖了关键系统文件的详细介绍，如： - **access_listsFile**：用于管理用户和组的访问权限列表。 - **acct.cfgFile**：与用户账户计费和审计有关的配置文件。 - **adminFile**：可能涉及到系统管理工具和配置的高级操作。 - **aliasesFile for Mail**：邮件系统中的别名文件，用于电子邮件地址映射。 - **auditFile for BNU**：可能是与安全审计相关的文件，特别是与业务网络单元（Business Network Unit）的活动监控。 - **/etc/security/authorizationsFile**：权限控制和授权的设置文件。 - **autosecretsFile**：自动密码管理文件，可能与身份验证和加密有关。每个文件的介绍包括文件用途、结构、重要参数和管理注意事项。此外，文档还强调了AIX的特性，如： - **Casesensitivity in AIX**：AIX操作系统对于大小写敏感性的处理规则，这对于正确识别和操作文件至关重要。 - **ISO9000**：可能提到文档遵循ISO 9000质量管理体系标准，保证信息的准确性和一致性。这份文件参考说明是AIX 7.1管理员和开发人员的必备参考资料，提供了一个全面的指南来管理和操作系统的各个方面，确保用户能够高效、安全地使用AIX 7.1环境。

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.

6 AIX Version 7.1: Files Reference

Related reference:

“depend File” on page 73

“pkginfo File” on page 224

Related information:

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.

Berkeley DB support is now available on AIX 5.1 for Sendmail 8.11.0. 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

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 10.

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.

Files Reference 9

剩余1099页未读，继续阅读

allance

粉丝: 0
资源: 12

AIX 7.1文件参考手册更新及系统关键内容概览

aix 7.1 iso bt种子下载

AIX操作系统(中文)

AIX7.1系统文档

rsync 下载 aix7.1

db2 v11下载aix7.1

AIX7.1最大支持多少cpu核心数

aix 7.1 lsof

aix7.1 nohup /usr/sbin/syncd 10 > /dev/null 2>&1 &

aix7.1安装oracle 11gr2

aix 查看文件大小

最新资源