Open System Services Management and Operations Guide (G06.29+, H06.07+)

Managing Security
Open System Services Management and Operations Guide—527191-005
8-17
Assigning an Initial Working Directory
Figure 8-2. TACL Macro to Configure an OSS User (page 1 of 2)
?TACL MACRO
==
== This unnamed macro adds FTP user logins to the system.
==
==
#FRAME
#SET #INLINEPREFIX>
INLECHO ON
==
==
SAFECOM /INLINE/
==
==
== Add a user definition for the user LINDA in user group
== SCRIBE.
==
== This definition provides the user with only Guardian access
== and is appropriate for a user who wants initial FTP
== access to the Guardian file system.
==
== The lack of an INITIAL-DIRECTORY value in the following user
== definition causes the Guardian default volume and subvolume
== to become the OSS initial working directory.
>ADD USER scribe.linda, 168,10, PASSWORD Abcdef1
==
== Assign the user definition appropriate Guardian file
== security:
>ALTER USER scribe.linda, GUARDIAN DEFAULT SECURITY NUNU
==
== Assign the user definition appropriate Guardian default
== volume and subvolume names:
>ALTER USER scribe.linda, GUARDIAN DEFAULT VOLUME $data2.q9552
==
== Display the configuration for the primary user definition:
>INFO USER scribe.linda, DETAIL
==
==
== Add an alias named lindaw for the user definition.
==
== This alias is used for either OSS or Guardian environment
== access.
==
== Assign the same password as for the user definition, to
== avoid user confusion.
>ADD ALIAS lindaw, 168,10, PASSWORD Abcdef1
==
== Assign the alias appropriate Guardian file security:
>ALTER ALIAS lindaw, GUARDIAN DEFAULT SECURITY NUNU
==
== Assign the alias consistent Guardian default volume and
== subvolume names:
>ALTER ALIAS lindaw, GUARDIAN DEFAULT VOLUME $data2.q9552
==
== Assign the alias an initial program to run in the OSS
== environment, in case of access through a direct service:
>ALTER ALIAS lindaw, INITIAL-PROGRAM /bin/sh
==
== Assign the alias an OSS initial working directory:
>ALTER ALIAS lindaw, INITIAL-DIRECTORY /home/lindaw
==