mktrigger

By means of a trigger inheritance scheme, newly created elements (but not existing elements) inherit the triggers that are currently associated with their parent directory element. But a simple inherit-all-triggers strategy does not suit the needs of many sites. For example:

• You may not want some of a directory's triggers to propagate to its subtree.
• You may want some triggers to fire only for file elements, not for directory elements.

To enable such flexibility, each directory element has two independent lists of trigger types:

• Its attached list specifies triggers that fire on operations involving the directory element.
• Its inheritance list specifies triggers that elements created within the directory inherit.

By default, attaching a trigger to a directory element updates both lists:

Each file element has only an attached list:

You can use the –ninherit and –nattach options to control exactly which triggers on a directory element are inherited. (And you can make adjustments using the –ninherit and –nattach options of the rmtrigger command.)

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.

Default

If a pname argument names a directory element, the trigger is attached only to the element itself, not to any of the existing elements within it.

–r/ecurse

Processes the entire subtree of each pname that is a directory element (including pname itself). On UNIX and Linux, VOB symbolic links are not traversed during the recursive descent into the subtree.

Default

For a directory element, the specified trigger type is placed both on the element's attached list and its inheritance list. (For a file element, the trigger type is placed on its attached list, which is its only trigger-related list.) The following options apply to directory elements only.

–nin/herit

The trigger is placed on the element's attached list, but not on its inheritance list. This option is useful when you want to monitor operations on a directory, but not operations on the files within the directory.

–nat/tach

The trigger is placed on the element's inheritance list, but not on its attached list. This option is useful when you want to monitor operations on the files within a directory, but not operations on the directory itself.

Default

If trigger-type-name is defined with a restriction to one or more object types, mktrigger refuses to process an object of another type.

–f/orce

Attaches a trigger to an object whose type does not match the definition of the trigger type. Such a trigger does not fire unless you change the object's type (chtype) or you redefine the trigger type (mktrtype –replace).

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	Path name 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)

Default

None.

pname ...

One or more path names, specifying elements to which the specified trigger type is to be attached.

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 object type
vob-selector	UCM project VOB specifier Specify vob-selector in the form [vob:]pname-in-vob
	pname-in-vob	Path name 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)