Product | Command Type |
---|---|
ClearCase | general information |
ClearCase LT | general information |
Attache | general information |
MultiSite | general information |
Platform |
---|
UNIX |
Windows |
In general, only commands that modify (write to) a VOB or a project VOB are subjected to identity checking. The following hierarchy of identity checking is used, in a command-specific manner, to determine whether a command can proceed or be canceled:
All products on UNIX only-root
All products except ClearCase LT on Windows only-member of the ClearCase group
ClearCase LT on Windows only-local administrator of the ClearCase LT server host
NOTE: We strongly recommend that you do not make ordinary ClearCase users members of the ClearCase group, nor allow ClearCase LT users to log on as the local administrator at the ClearCase LT server host.
VOB owner
Owner of the relevant element (for modifications to branches and versions)
Owner of the relevant type object (for modifications to objects of that type)
Creator of a version or derived object
Owner of the object (pool, hyperlink, replica, activity, checkpoint, domain, role, state, user)
User associated with an event
Members of an object's group (same group-ID)
Both file-system and non-file-system objects have an owner and a group; this information is storedwith the object. When an object is created, its owner and group are set to that of the user who created it. Use the protect command to change the owner (-chown) or group (-chgrp) of the object. The describe command displays the owner and group of the object.
The scheduler maintains its own access control list (ACL),which determines who is allowed access to the scheduler and to the ACL itself. See the schedule reference page for more information.
The reference page for a command lists the special identities (if any) required to use the command along with other restrictions on its use.
The sections below list all cleartool subcommands and Attache commands, categorized by their identity requirements. For information on identity checking for ClearCase and ClearCase LT commands (that is, other than cleartool subcommands and Attache commands), refer to the corresponding reference pages.
annotate checkvob (except with -fix or -hlink) dospace 1 endview (except with -server) import 3 | ln 4 |
mkattype 5 mkbrtype 5 mkdir 4 mkelem 4 mkeltype 5 mkhltype 5 mklbtype 5 mktag 6 mkview 7 mkvob 7 mount 10 mv 4 |
reqmaster (requesting mastership only) 9 rmname 4 8 space 1 umount (public VOB) |
1 Except with -update or -generate | |||
2 No special identity required for "search" functionality | |||
3 For created elements only | |||
4 One or more directory elements must be checked out | |||
5 Except with -replace | |||
6 Except for private VOB-tag | |||
7 Standard UNIX/Windows NT permissions for creating a subdirectory required | |||
8 Except with -nco | |||
9 Must be on ACL at master replica | |||
10 Only for public VOB |
checkvob -hlink import 1 merge 2 | |||
1 For checked-out directories only 2 Applies to creation of merge arrows only, not to data |
chtype (element) lock (element) |
unlock (element) |
chtype (branch) lock (branch) |
unlock (branch) |
lock (type object) mkattype -replace mkbrtype -replace mkeltype -replace mkhltype -replace | mklbtype -replace mktrtype -replace rename (type object) unlock (type object) |
rename (pool) |
NOTE: Only the VOB owner and root, members of the ClearCase group can delete a shared derived object.
endview -server | setcache -view space -view -generate |
|
checkvob -fix dospace -generate ln -nco lock (pool or VOB) mktrtype 1 |
reqmaster (to set access controls) rmname -nco space -vob -generate umount (private VOB) unlock (pool or VOB) |
1 except with -replace |
checkvob -fix ln -nco lock (pool or VOB) mktrtype 1 |
rmname -nco space -vob -generate unlock (pool or VOB) |
1 except with -replace |
mktag (private VOB-tag)
mount (private VOB)
chview (can also be root on view server host)
setcache -host | setcache -mvfs |
dospace -update | space -update |
Reference pages for individual commands
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |