alter the watchdog timeout before push_remote and after, due to possible long io

Change-Id: Ibddf830dbed8ee36c75113267645a576e38efa31
Signed-off-by: Yaroslav Brustinov <ybrustin@cisco.com>

1 files changed, 11 insertions, 0 deletions

diff --git a/src/rpc-server/commands/trex_rpc_cmd_general.cpp b/src/rpc-server/commands/trex_rpc_cmd_general.cpp
index d4854a79..82cbaca1 100644
--- a/src/rpc-server/commands/trex_rpc_cmd_general.cpp
+++ b/src/rpc-server/commands/trex_rpc_cmd_general.cpp
@@ -649,12 +649,23 @@ TrexRpcCmdPushRemote::_run(const Json::Value &params, Json::Value &result) {
     }
 
 
+    /* IO might take time, increase timeout of WD */
+    TrexMonitor * cur_monitor = TrexWatchDog::getInstance().get_current_monitor();
+    if (cur_monitor != NULL) {
+        cur_monitor->io_begin();
+    }
+
     try {
         port->push_remote(pcap_filename, ipg_usec, min_ipg_sec, speedup, count, duration, is_dual);
     } catch (const TrexException &ex) {
         generate_execute_err(result, ex.what());
     }
 
+    /* revert timeout of WD */
+    if (cur_monitor != NULL) {
+        cur_monitor->io_end();
+    }
+
     result["result"] = Json::objectValue;
     return (TREX_RPC_CMD_OK);