Although I like RunRev for its ease of creating GUI interfaces that I can incorporate with shell scripted processing, it doesn't take advantage of the *Nix ability to run concurrent and background processes, so that one has to wait for a launched shell script to terminate before RunRev hands control back to the user.
You can get around this by starting up some Linux shell script daemons prior to launching the RunRev application, use a launched script in RunRev that does something the daemon is waiting for, then terminates immediately, and it will return control to the application. Since the daemons can be made to sleep and only wake periodically to see if a variable is set, or a file is not empty, or it's modification time is changed, etc, they are a low overhead method of performing parallel activities for a RunRev application.
You can use this method to play sounds using a Linux player, run a screen hack in the root window, process a long time analysis, collect real time data, all without the RunRev interface getting involved.
What a great workbench Linux gives us, there is always a solution somewhere in its bag of shell tricks without having to be a tech head programmer.
javascript:emoticon(':D')
Background shell script processes
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Background shell script processes
Stomfi
Brisbane
Australia
Brisbane
Australia