auto-bounce thread based off alerts not very clean

Luke,

You should be able to do this via an alert.  I would recommend putting the stop & start as one exec action (separated by a semi-colon).  That way the start will execute after the stop has completed.  Simply choose the exec action, and enter the standard hci commands in the Command dialogue box –

hcicmd -p p_other -c “problem_thread pstop”;hcicmd -p p_other -c “problem_thread pstart”

Hope this helps.

Jim Cobane

Henry Ford Health

I would review the alerts.log ($HCISITEDIR/exec/hcimonitord/alerts.log) and see if there is any indication in there if the exec action failed.

Jim Cobane

Henry Ford Health

I have been able to successfully execute stop and start commands from an alert I created. I have set it up in this fashion.

exec {hcicmd -p hbo_test -c ‘to_nscall_adt pstop’}

tcl{sleep 10}

exec {hcicmd -p hbo_test -c ‘to nscall_adt pstart’}

It seems to work very well with no problems(so far).

Almost every alert we fire for an interface calls our KSH script to cycle the thread and I never noticed the issue you described.

I see we have a 5 second sleep between the stop and start which might help with your problem.

We are running cloverleaf 5.6rev2 on AIX 5.3.

Here is the code snippet of interest

#————————————–
# define functions local to this script
#————————————–

function recycle_thread {

[code]#

---

# define functions local to this script
#

---

function recycle_thread {

since you’re on 5.8, you could also use

hcicmd -p $process_name -c”$thread_name prestart”

instead of the pstop, sleep, pstart.  then cloverleaf will take care of the timing for you.

I don’t think the sleep invoked from the alerts puts the process to sleep that I’m aware of.

If something called from within a cloverleaf process like a TPS proc does a sleep that will put the entire cloverleaf process to sleep.

your post on using a ping to do a sleep sounded familar to me.

I looked and my perpetual looping bat file to ping once a minute to keep my VPN connection from timing out, which uses the ping to sleep 60 seconds before pinging again.

You would think the DOS operating system would have a sleep but I ended up using the ping, too.

@echo off
:START
[code]@echo off
:START