[philip rake]

That seems to have done the trick, thank you! I also added MAILTO=”” so I can run it every 10 minutes without filling up the mail.  Hopefully this all works, thanks, all.

[philip rake]

I went a slightly different route with this and wrote a .tcl that errors the blank message. Then a shell script that processes the hcidbdump -e to resend the good message. Works great, until I try to Linux cron it.  It either can’t find hcidbdump, or I get a error (hcidbdump: error while loading shared libraries: libxerces-c.so.27: cannot open shared object file: No such file or directory). Is it possible to run hcidbdump  from cron invoked script?

[philip rake]

Thank you both for your responses.  Its 5.8 and one message per file.  Concerning the Directory Parse option David mentions, its the canned script that does this –

set msg_list [msgget $mh]
set msg_list [split $msg_list ” “]
set msg_list [lsort -increasing $msg_list]
msgset $mh $msg_list
return “{CONTINUE $mh}”
}

time {
# Timer-based processing
# N.B.: there may or may not be a MSGID key in args
}

 

I would put something in there to pull in and evaluate the file’s time stamp?

Thanks, again,

Phil

[Author]

Replies