I've been tired from not understanding why a background process is being killed after a time!
[i] ./iperf -s -u -D (this by itself should stay alive until I give a kill command, the -D option in the command tells the iperf to run as a daemon)
[ii] ./iperf -s -u > foo.out 2> foo.err < /dev/null & (even this killed; I removed the -D and run the normal command as a background process, but no success)
[iii] ./iperf -s -u -D > foo.out 2> foo.err < /dev/null & (this might sound not correct logically to run a daemon that is by itself a background process as a background a gain, but also failed with some hosts)
If any one can help to write a short script that will run as a background or whatever correct to check ALWAYS for iperf. If it finds alive, do nothing; else runs iperf again as quick as possible to avoid any requests form other hosts in this off-time.