Good day mc_,
Actually we timed it so that the captures are running, while we start our script, keeping a very close eye on the start/stop times. Since the script seems to end successfully (even with timeouts), what we observed are run times in the 5-6 seconds (no timeouts) to various times up to 1m35s (with 2-3 timeouts), but it ends while these timeouts will indicate that a few graphical files could not be either founf or saved, as seen in the unsuccessful_run_output.txt file submitted earlier.
Addendum: our environment is a test one, so we can (re-)start or stop anything, anytime for our testing purposes.
Question: from the tcpdump file, anything we can pull from the several timeout statuses logged in there ?