- This topic has 4 replies, 2 voices, and was last updated 13 years, 5 months ago by
.
-
Topic
-
I have some problems in writing automatic bouncing thread when it is dead. in command line, when I type hcicmd -p processA -c “from_singlethread pstop”, the thread stops, then I type hcicmd -p processA -c “from_singlethread pstart”, the thread starts.
I am trying to embed this command in Alert. When certain alert criteria meets, then execute exec hcicmd -p processA -c “from_singlethread pstop”and then exec hcicmd -p processA -c “from_singlethread pstart”. However, it does not work. Do you have any idea what’s wrong?
-
Replies
-
-
Ran,
I would do this as 1 exec action:
exec hcicmd -p processA -c “from_singlethread pstop”;hcicmd -p processA -c “from_singlethread pstart”
The semi-colon treats these as separate commands within the same exec action. The second command won’t execute until the first completes. I think in your configuration, the ‘start’ may be executing before the ‘stop’ is complete.
Hope this helps.
Jim Cobane
Henry Ford Health
-
Actually I tried to only use exec hcicmd -p processA -c “from_singlethread pstop”, but the thread did not stop, while I type this command in command line, the thread stops immediately.
James Cobane wrote:Ran,
I would do this as 1 exec action:
exec hcicmd -p processA -c “from_singlethread pstop”;hcicmd -p processA -c “from_singlethread pstart”
The semi-colon treats these as separate commands within the same exec action.
-
Ran,
Instead of double quotes, try enclosing the -c parameter in single quotes:
exec hcicmd -p processA -c ‘from_singlethread pstop’;hcicmd -p processA -c ‘from_singlethread pstart’
This is how we have our alerts defined that are bouncing threads. You might want to look in the hcimonitord.log to see if there are any errors when attempting the exec action.
Jim Cobane
Henry Ford Health
-
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
