05-17-2009
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
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Has anybody been able to execute a shell script call from a database trigger?
If so what are the steps to execute it? Do we have any specific packages in Oracle?
Reards,
Rahul. (1 Reply)
Discussion started by: rahulrathod
1 Replies
2. Shell Programming and Scripting
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 Replies)
Discussion started by: zooby
4 Replies
3. UNIX and Linux Applications
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... (0 Replies)
Discussion started by: kalinkula
0 Replies
4. HP-UX
Hi, I'm totally new in Control-M and I really need some help. Here's my problem.
I need to make job X from a server trigger job Y from a different server where job X must receive a confirmation first before execution. :confused:
I really have no idea on how to do that so can you please give... (1 Reply)
Discussion started by: criphaze22
1 Replies
5. Shell Programming and Scripting
Hi,
I want a script , which searches the log for the term/phrase "JFSnapshotService::systemSnapshot: Starting data capture. This may take awhile depending upon system workload." and if there is some logging like this, it has to mail me that this data capture process is happening.,
Below is... (2 Replies)
Discussion started by: cratercrabs
2 Replies
6. Shell Programming and Scripting
have three big data file, however I just need to see the mentioned below one line form the all the file which has SERVER_CONNECTION Value
File 1
export SERVER_CONNECTION=//dvlna002:10001/SmartServer
File2
export SERVER_CONNECTION=///SmartServer
File3
export... (1 Reply)
Discussion started by: Nsharma3006
1 Replies
7. OS X (Apple)
Hi all...
Has _below_ ever been done in UNIX shell scripting before?
(I have done this easily in Python but this is using purely the shell.)
The DEMO version IS built and has been tested.
Pre-amble...
I now need at least one control pulse for the AudioScope.sh when in PURELY audio I/O mode,... (2 Replies)
Discussion started by: wisecracker
2 Replies
8. Shell Programming and Scripting
Hi,
I'm looking for a way to solve the following scenario:
A shell should automatically trigger / run when a text file is placed or present at a specific location.
My idea - to create a cron / anacron for every minute and inside that i will call a temp script. Temp script will move to my... (9 Replies)
Discussion started by: Gautham
9 Replies
9. Shell Programming and Scripting
mainpid=$$
(trap "echo timeout" SIGTERM SIGKILL SIGINT; sleep 5; kill $mainpid) &
watchdogpid=$!
sleep 10 #do something
kill $watchdogpid
I design a timeout function script
I don't see the echo "timeout" is on the screen (1 Reply)
Discussion started by: yanglei_fage
1 Replies
10. Shell Programming and Scripting
Hi Guys,
I have a main_script.sh which runs every day and scheduled in crontab.
in the main script i read data from config file
test.config
apple
mango
orange
main_script.sh
for i in `cat test.config`
do
if
then
echo 'Apple' (3 Replies)
Discussion started by: Master_Mind
3 Replies
LEARN ABOUT MOJAVE
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)