Searched hist:"3 e1d3678844b2b1f4c41818bc9a2885cbf5ccef6" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/tools/testing/ktest/ |
| H A D | sample.conf | diff 3e1d3678844b2b1f4c41818bc9a2885cbf5ccef6 Wed Mar 21 09:36:08 CDT 2018 Steven Rostedt (VMware) <rostedt@goodmis.org> ktest: Add CONNECT_TIMEOUT to change the connection timeout time
Before ktest issues a reboot, it will try to connect to the target machine
to make sure that it is still alive. If the target does not respond within 5
seconds, it will power cycle the box instead of issuing a reboot.
Five seconds may be too short, and ktest may unnecessarially power cycle the
box. I have found 25 seconds seems to be a better timeout for this purpose.
But even 25 may be too arbitrary. Add a CONNECT_TIMEOUT option to let the
user determine the timeout time before rebooting. By default, it has been
raised to 25 seconds.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
|
| H A D | ktest.pl | diff 3e1d3678844b2b1f4c41818bc9a2885cbf5ccef6 Wed Mar 21 09:36:08 CDT 2018 Steven Rostedt (VMware) <rostedt@goodmis.org> ktest: Add CONNECT_TIMEOUT to change the connection timeout time
Before ktest issues a reboot, it will try to connect to the target machine
to make sure that it is still alive. If the target does not respond within 5
seconds, it will power cycle the box instead of issuing a reboot.
Five seconds may be too short, and ktest may unnecessarially power cycle the
box. I have found 25 seconds seems to be a better timeout for this purpose.
But even 25 may be too arbitrary. Add a CONNECT_TIMEOUT option to let the
user determine the timeout time before rebooting. By default, it has been
raised to 25 seconds.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
|