Searched hist:"212 aefaa53d142baa9a22f5aadd2e72eb916c0c0" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/qemu/block/ |
| H A D | curl.c | diff 212aefaa53d142baa9a22f5aadd2e72eb916c0c0 Wed Aug 13 10:44:27 CDT 2014 Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com> block.curl: adding 'timeout' option
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the remote server configuration and network
traffic. The user should be able to set how much long he is
willing to wait for the connection.
Adding a new option to set this timeout gives the user this
flexibility. The previous default timeout of 5 seconds will be
used if this option is not present.
Reviewed-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
Reviewed-by: Benoit Canet <benoit.canet@nodalink.com>
Tested-by: Richard W.M. Jones <rjones@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
|
| /openbmc/qemu/ |
| H A D | qemu-options.hx | diff 212aefaa53d142baa9a22f5aadd2e72eb916c0c0 Wed Aug 13 10:44:27 CDT 2014 Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com> block.curl: adding 'timeout' option
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the remote server configuration and network
traffic. The user should be able to set how much long he is
willing to wait for the connection.
Adding a new option to set this timeout gives the user this
flexibility. The previous default timeout of 5 seconds will be
used if this option is not present.
Reviewed-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
Reviewed-by: Benoit Canet <benoit.canet@nodalink.com>
Tested-by: Richard W.M. Jones <rjones@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
|