bakunin,
This appears to be a question that will never die.
I have since found a way (by creating a daemon that checks the logfile for any changes, every 20 seconds or so) to rig a solution, but everyone involved in the project keeps bringing up this trigger mechanism again and again.
It seems they are determined that I do it that way.
All I can say is one of the techs played around with this briefly and suggested creating a fifo pipe file. This is something I have never done, or been told to do, in about a decade and a half of UNIXing. Sorry, it just has never come up.
Apparently it works something like this:
#!/usr/bin/sh
exec 0 < log_pipe #log_pipe is a pipe made using the mkfifo cmd
while :
do
while read LINE
sleep 1
done
The only thing I can possibly understand about a fifo file is that it simply sits with the contents of one action and waits for another, such as:
ls | pg
you can mkfifo pipe_listing then:
ls > pipe_listing
then pg < pipe_listing sometime later.
Any of this make any sense?
Everyone says that they can't understand why I am not going htis route, but no one can say how................can't figure it out for anything................