Stopping interfaces on NACK

[Jason Russell]

So as far as I’m aware, Cloverleaf’s default behavior is to attempt to send x number of times, throw it in the error database, and then move on. However, I’m wanting to shut down the interface on a non-ACK.

[code]
# Init counter
set send_cnt 0

# Tell em bout it and put reason in metadata
echo “\n$module: Three consecutive AR\
responses – $ackmsg”
echo “Message to Error Database”
echo “Reply is:”
echo $msg\n\n
echo “Message is:”
echo [msgget $my_mh]\n

# Put reason in metadata and send message to
# Error database

msgmetaset $my_mh USERDATA “Exceeded\
Application Reject (AR) retrys – $ackmsg”

return “{KILLREPLY $mh} {ERROR $my_mh}”
[/code]

While I am planning on putting an email proc call in there, can I call the hcienginestop (or other command), or should I be looking to shut these down in another way?

Topic

[Charlie Bursell]

You can certainly call hcienginestop stop with an exec command. The good thing about this command is, if the process is hung, it will eventually kick it to death. It is much better than trying to stop the thread which may not happen if the engine is busy and all sorts of weirdness will ensue.

FWIW. It is NOT the default of Cloverleaf to resend X number of times then error to the Error Database. The default of the engine is to keep resending forever. It is the reply proc you are using that modifies this behavior. The proc is furnished as a tool that can be modified as you see fit for your usage. I would recommend you copy the proc and rename if you do that.

[Jason Russell]

Thank you, that just helps validate what I was looking at doing. Time to get to testing!

[Author]

Replies