Calling and catching a trigger

shayak has asked for the wisdom of the Perl Monks concerning the following question:

Their are two scripts a1.pl and a2.pl; A2.pl is called by a1.pl; Now when a2.pl is running and if it encounters a condition, i want to trigger an alarm to a1.pl; Now when the trigger is called a1.pl executes a function. In the meantime a2.pl keeps on running and keeps on sending triggers wherever required without stopping. And a1.pl runs the particular functions for the triggers. How to do this? Another info. A1.pl is in the host machine and a2.pl is in a VM. I want to know exactly how can we give the trigger(alarm)from a2.pl and catch it with the main script a1.pl?

Comment on Calling and catching a trigger

Replies are listed 'Best First'.
Re: Calling and catching a trigger by Anonymous Monk on Jun 20, 2011 at 14:59 UTC
Remember all those GUI automation questions you had? All they're doing is sending messages (its like signals) to programs. You can do this too.	[reply]
Re^2: Calling and catching a trigger by shayak (Novice) on Jun 20, 2011 at 15:04 UTC
I want to know how can i do it when the script is continuosly running?	[reply]
Re^3: Calling and catching a trigger by Anonymous Monk on Jun 20, 2011 at 15:07 UTC
Whether or not the script is continuously running, makes no difference.	[reply]
Re: Calling and catching a trigger by NetWallah (Canon) on Jun 21, 2011 at 05:25 UTC
What you are attempting sounds a lot like an SNMP Trap send and receive system. Configure snmpd to receive the trap, and call your 'a.pl'. When you need to send the trap, have your 'b.pl' call snmptrap to send it. Much complexity, features and cruft can be added, once the basic system starts working. "XML is like violence: if it doesn't solve your problem, use more."	[reply]
Re^2: Calling and catching a trigger by Anonymous Monk on Jun 21, 2011 at 10:09 UTC
Or even Growl Network Transport Protocol / Growl::GNTP	[reply]
Re: Calling and catching a trigger by aquarium (Curate) on Jun 21, 2011 at 04:43 UTC
that sort of architecture is typically but not always quite messy. instead design a third program, which has a proper interface to be a controller of sorts. that way you can get some sanity the hardest line to type correctly is: stty erase ^H	[reply]