rmtrigger
Removes trigger from an element or UCM object
Applicability
Product |
Command type |
---|---|
VersionVault |
cleartool subcommand |
Platform |
---|
UNIX® |
Linux® |
Windows® |
Synopsis
- rmtrigger [ –c/omment comment | –cfi/le comment-file-pname |–cq/uery
- | –cqe/ach | –nc/omment ]
[ –nin/herit | –nat/tach ] [ –r/ecurse ]
trigger-type-selector { pname | ucm-object-selector } ...
Description
The rmtrigger command removes an attached trigger from one or more elements or UCM objects. The specified trigger-type-selector is not affected by rmtrigger. To delete the trigger type, use the rmtype command.
Restrictions
ACL authorization
- read-info on VOB object
- mod-trig on element
Non-ACL authorization
You must have one of the following identities:
- Object owner
- Object group member
- VOB owner (for an element trigger)
- Project VOB owner (for a UCM object trigger)
- root (UNIX® and Linux®)
- Member of the VersionVault administrators group (VersionVault on Windows®)
Locks
An error occurs if one or more of these objects are locked: VOB (for an element trigger), project VOB (for a UCM object trigger), object type, object, trigger type.
Mastership
(Replicated VOBs only) No mastership restrictions.
Options and arguments
Event records and comments
- Default
- Creates one or more event records, with commenting controlled by your .versionvault_profile file (default: –nc). See the comments reference page. Comments can be edited with chevent.
- –c/omment comment | –cfi/le comment-file-pname |–cq/uery | –cqe/ach | –nc/omment
- Overrides the default with the option you specify. See the comments reference page.
Manipulating the trigger lists of a directory element
- Default
- The trigger is removed from both of a directory element's trigger lists: its attached list and its inheritance list.
- –nin/herit
- (Directory element only) The trigger is removed from the directory's attached list, but remains on its inheritance list. The trigger does not fire when the monitored operation is performed on the directory itself, but new elements created in that directory inherit the trigger.
- –nat/tach
- (Directory element only) The trigger is removed from the directory's inheritance list, but remains on its attached list. The trigger continues to fire when the monitored operation is performed on the directory itself, but new elements created in that directory do not inherit the trigger.
Removing triggers from an entire subdirectory tree
- Default
- If a pname argument names a directory element, the trigger is removed only from the element itself, not from any of the existing elements within it.
- –r/ecurse
- Processes the entire subtree of each pname that is a directory element (including pname itself). UNIX® and Linux® VOB symbolic links are not traversed during the recursive descent into the subtree.
Specifying the trigger type
- Default
- None.
- trigger-type-selector
- The name of an existing element trigger type. Specify trigger-type-selector in
the form [trtype:]type-name[@vob-selector]
trigger-type-selector
type-name
Name of the trigger type
vob-selector
VOB specifier
Specify vob-selector in the form [vob:]pname-in-vob
pname-in-vob
Pathname of the VOB tag (whether or not the VOB is mounted) or of any file system object within the VOB (if the VOB is mounted)
Specifying the element
- Default
- None.
- pname ...
- One or more pathnames, specifying elements from which triggers (instances of the specified trigger type) are to be removed.
Specifying the UCM object
- Default
- None.
- ucm-object-selector ...
- The name of the UCM object. Specify ucm-object-selector in
the form [ucm-object-type:]type-name[@vob-selector]
ucm-object-selector ...
ucm-object-type
Name of the UCM type
vob-selector
UCM project VOB specifier
Specify vob-selector in the form [vob:]pname-in-vob
pname-in-vob
Pathname of the project VOB tag (whether or not the project VOB is mounted) or of any file system object within the project VOB (if the project VOB is mounted)
Examples
The UNIX system and Linux examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
- Remove an attached trigger from hello.c.
cmd-context rmtrigger trig1 hello.c
Removed trigger "trig1" from attached list of "hello.c". - Remove an attached trigger from
the src directory's attached list, but leave
it in the inheritance list.
cmd-context rmtrigger –ninherit trig1 src
Removed trigger "trig1" from attached list of "src". - Remove an attached trigger from
the release directory's inheritance list, but
leave it in the attached list.
cmd-context rmtrigger –nattach trig1 release
Removed trigger "trig1" from inheritance list of "release".