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)
HI,
I have a script which will be running all the time...it is like a trigger.. wakesup every 10 minutes(trigger.sh) executes, and I want to write another script which monitors this script every one hour and if it finds that trigger script is not running it should start it and exit...and here... (9 Replies)
Hello all,
I'm new to shell programming and need some help. I would like to set up a step within a shell script to trigger another shell script to run, based on the highest return code generated in the current script. For example, if the highes return code value in the current script is less... (1 Reply)
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. (8 Replies)
I need to execute my script as soon as one log file arrives.
This log file is named as logyymmdd. I need to add trigger to my script based on this logfile.
Please guide. (1 Reply)
Hello Friends,
I've been searching solutions for an exceptional backup case recently, I need someone to guide me, suggest a method pls.
In a production system we have backup scripts, they are run by cron one after another, and monthly. There is 1 hour difference between each consecutive script... (1 Reply)
Hi,
I have been assigned a job which requires me to send mails from unix(Mailx) upon on certain actions triggered in the database.
On insert/update of a certain field into one of the database tables the shell script present in Unix box responsible to send mail though mailx needs to be triggered... (7 Replies)
Hi
I have created a shell program, which takes a series of parameters as shown in the below code. Its working good from terminal.
My program
restorejob.sh -g <NAME> -p <Path-to-search> -r <Path-to-restore>
Its working fine from bash shell.
I want to extend this functionality like... (1 Reply)
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)
Hi Guys,
I am having below code which runs based on condition, Is it possible to check condition at the time of trigger
code=$1
if ;then
nohup sh script.sh $val 1 &
fi
I need to trigger if the $code = JP then only to trigger nohup sh script.sh $val 1 &
My try but wanted... (4 Replies)
Discussion started by: Master_Mind
4 Replies
LEARN ABOUT XFREE86
dpkg-trigger
dpkg-trigger(1) dpkg suite dpkg-trigger(1)NAME
dpkg-trigger - a package trigger utility
SYNOPSIS
dpkg-trigger [option...] trigger-name
dpkg-trigger [option...] command
DESCRIPTION
dpkg-trigger is a tool to explicitly activate triggers and check for its support on the running dpkg.
This can be used by maintainer scripts in complex and conditional situations where the file triggers, or the declarative activate triggers
control file directive, are insufficiently rich. It can also be used for testing and by system administrators (but note that the triggers
won't actually be run by dpkg-trigger).
Unrecognized trigger name syntaxes are an error for dpkg-trigger.
COMMANDS --check-supported
Check if the running dpkg supports triggers (usually called from a postinst). Will exit 0 if a triggers-capable dpkg has run, or 1
with an error message to stderr if not. Normally, however, it is better just to activate the desired trigger with dpkg-trigger.
-?, --help
Show the usage message and exit.
--version
Show the version and exit.
OPTIONS --admindir=dir
Change the location of the dpkg database. The default location is /var/lib/dpkg.
--by-package=package
Override trigger awaiter (normally set by dpkg through the DPKG_MAINTSCRIPT_PACKAGE environment variable of the maintainer scripts,
naming the package to which the script belongs, and this will be used by default).
--no-await
This option arranges that the calling package T (if any) need not await the processing of this trigger; the interested package(s) I,
will not be added to T's trigger processing awaited list and T's status is unchanged. T may be considered installed even though I
may not yet have processed the trigger.
--await
This option does the inverse of --no-await (since dpkg 1.17.21). It is currently the default behavior.
--no-act
Just test, do not actually change anything.
EXIT STATUS
0 The requested action was successfully performed. Or a check or assertion command returned true.
1 A check or assertion command returned false.
2 Fatal or unrecoverable error due to invalid command-line usage, or interactions with the system, such as accesses to the database,
memory allocations, etc.
ENVIRONMENT
DPKG_ADMINDIR
If set and the --admindir option has not been specified, it will be used as the dpkg data directory.
SEE ALSO dpkg(1), deb-triggers(5), /usr/share/doc/dpkg-dev/triggers.txt.gz.
1.19.0.5 2018-04-16 dpkg-trigger(1)