Trigger executable on HMC on occurence of an event Post: 302924928

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Can we trigger an shell script on an event

Hi, My program A updates a log called logA. I have a shell script S that is responsible to send emails reading from the log. I want to trigger execution of the script whenever there is an update to the log. Thanks in advance.

2. Shell Programming and Scripting

Trigger Enter

Hello, I need to trigger every time enter has been clicked while some one on terminal i tried to googleit but with out result any idea ?? thanks in advance

3. Shell Programming and Scripting

Trigger with condition

If test.ksh is successful then I have a sequence of script which needs to execute automatically. Is it possible to capture the return code to execute the next script automatically? what is better way of doing this.

4. UNIX and Linux Applications

update trigger

hi all, i hope i am posting this /beginner) question in the right forum: i want to create an update trigger, which rolls back a transaction if a record of a table is updated. the table has - amongst others - a field 'statusid' - if a record in this table has the statusid X and it is attempted...

5. Shell Programming and Scripting

Print between patterns - first occurence, second occurence etc

I have a file # cat asasas AAAAAA 11 22 33 44 BBBBB NILNILNIL AAAAAA 22 33 44 55 66 77 88 BBBBB NILNILNIL

LEARN ABOUT X11R4

deb-triggers

deb-triggers(5) 						    dpkg suite							   deb-triggers(5)

NAME

       deb-triggers - package triggers

SYNOPSIS

       triggers

DESCRIPTION

       A  package  declares  its  relationship to some trigger(s) by including a triggers file in its control archive (i.e. DEBIAN/triggers during
       package creation).

       This file contains directives, one per line. Leading and trailing whitespace and everything after the first # on any line will be  trimmed,
       and empty lines will be ignored.

       The trigger control directives currently supported are:

       interest trigger-name
       interest-await trigger-name
       interest-noawait trigger-name

	      Specifies  that  the  package is interested in the named trigger. All triggers in which a package is interested must be listed using
	      this directive in the triggers control file. The "noawait" variant does not put the triggering packages in  triggers-awaited  state.
	      This should be used when the functionality provided by the trigger is not crucial.

       activate trigger-name
       activate-await trigger-name
       activate-noawait trigger-name

	      Arranges that changes to this package's state will activate the specified trigger. The trigger will be activated at the start of the
	      following operations: unpack, configure, remove (including for the benefit of a conflicting package), purge  and	deconfigure.   The
	      "noawait"  variant  does	not  put  the  triggering  packages  in triggers-awaited state. This should be used when the functionality
	      provided by the trigger is not crucial.

	      If this package disappears during the unpacking of another package the trigger will be activated when  the  disappearance  is  noted
	      towards  the  end  of the unpack. Trigger processing, and transition from triggers-awaited to installed, does not cause activations.
	      In the case of unpack, triggers mentioned in both the old and new versions of the package will be activated.

       Unknown directives are an error which will prevent installation of the package.

       The "-noawait" variants should always be favored when possible since triggering packages are not put in triggers-awaited state and can thus
       be  immediately	configured without requiring the processing of the trigger.  If the triggering packages are dependencies of other upgraded
       packages, it will avoid an early trigger processing run and make it possible to run the trigger only once as one of the last steps  of  the
       upgrade.

       The "-noawait" variants are supported since dpkg 1.16.1, and will lead to errors if used with an older dpkg.

       The "-await" alias variants are supported since dpkg 1.17.21, and will lead to errors if used with an older dpkg.

SEE ALSO

       dpkg-trigger(1), dpkg(1), /usr/share/doc/dpkg-dev/triggers.txt.gz.

1.19.0.5							    2018-04-16							   deb-triggers(5)