[Ken Smith]

Probably the last point. We have been gredually increasing the threads and processes in the site. But this has been an ongoing thing and all of a sudden the complaints started coming in about getting ADT messages only after a long delay.

[Ken Smith]

Send me an email and I’ll send you all I found out about this with screenshots and sample email message.

I kind of lost interest in this because the alerts seem to be inconsistent and we were diverted to more important stuff for the time being. There is an email link in my reply.

[Ken Smith]

Unfortunately, my company blocks access to that web site. Is there another way to get hold of that file? – Thanks!

[Ken Smith]

Incidentally – I *do* have to restart the monitor daemon after making changes to the tcl code.

[Ken Smith]

Hey, Bret!

Thanks for your feedback. I see where I was going wrong – I didn’t have the keylist variable set up properly – it’s the VALUE that triggers the message. Man, I’ve been working on getting this to work for quite a few hours – Thanks!

[Ken Smith]

I’d like to see resolution to this thread because I am seeing the same problem here. I basically did all the same things that Brian did and I’m getting the “invalid command name” error. I’m using the same default tcl code provided through the designer with a couple minor tweaks to the proc name, very basic, etc. and can’t get it to fire.

Additionally, it would be nice to know what exactly the Comparing: value is related to. I’ve tried 0 — I think that covers all bases — but the thing never fires. Of course, an invalid command name “my_test” could be preventing it, but it’s hard to say what is going on.

[Author]

Replies