IBM High Performance Storage System HPSS, Руководство по установке

Страница: 286 / 311

; 100MB = {
; BlockSize = 4MB
; StripeWidth= 0
; COS = 0
; }
; 1GB = {
; BlockSize = 8MB
; StripeWidth= 0
; COS = 0
; }
; }
# Use the System Password file routines (TRUE or FALSE)
# The Default for PFTP is FALSE ( Case Sensitive !)
Use System Password Files = FALSE
# Path and Name for the PFTP Password File
PFTP Password File = /var/hpss/etc/passwd
# Path and Name for the PFTP Shadow Password File
# NOTE: PFTP does not currently use the value. It is used ONLY to
# change how the password is looked up! If the site is using
# /etc/passwd and the system running the PFTP Daemon utilizes
# some form of "Shadow" password file to authenticate PFTP users,
# this should be uncommented.
# Do NOT remove the part after the "=" sign.
; PFTP Shadow File = /etc/security/passwd
# Path and Name for the PFTP Group File
; PFTP Group File = /etc/group
# Primary Authentication Type for the FTP Daemon authentication
; Primary Authentication Mechanism = KRB5
# Default: KEYTAB
; Primary Authenticator Type = KEYTAB
# Default: /var/hpss/etc/hpss.keytab
; Primary Authenticator = /var/hpss/etc/hpss.keytab
# Supported Client Authentication Mechanisms
# This mechanism will be used to authenticate the FTP client
# (end-user) with the FTP Daemon
# Values: GSS, GSI, USER_PASS, IDENT
# Default: USER_PASS && "Primary Authentication Mechanism"
# Mapfile Specifier specifies the type and required information
# for Mapping one user name to another. The types include
# "FILE:", "LDAP:", and "DBAS:" The default type is "FILE:"
# For "FILE:" specify the path and name of the file after the ":"
# Default Authorization Mechanism specifies the location of the
# pw_struct info. This may be "UNIX", "LDAP", or "DBAS"
# "DBAS" is NOT currently supported.
# This probably needs to be specified if a name mapping occurs.
# Use Site Auth Method is used to specify that the USER_PASS Mode is
# Overloaded and Hooks have been input to change the behaviour; e.g.,
# USER_PASS will actually use a Crypto Card to Authenticate. This is
# ONLY valid in the USER_PASS clause. NOTE: This is exactly as
# described: if this is specified for USER_PASS, it is impossible
# to allow both username/password AND usename/CryptoCard
simultaneously.
Client Authentication Mechanisms = {
; GSS = {
; Mapfile Specifier = FILE:/var/hpss/etc/KRB2UnixMapfile
; Use Site Auth Method = KRB5KDC
; Default Authorization Mechanism = LDAP
; }
HPSS Installation Guide July 2008
Release 6.2 (Revision 2.0) 286