whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Savu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (WHIRR-207) Handle curl timeouts better
Date Mon, 07 Feb 2011 16:59:57 GMT

    [ https://issues.apache.org/jira/browse/WHIRR-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991466#comment-12991466
] 

Andrei Savu commented on WHIRR-207:
-----------------------------------

>From the {{set}} manpage:

{code}
-e   errexit
          Exit immediately if a simple command exits with a non-zero
          status, unless the command that fails is part of an until or
          while loop, part of an if statement, part of a && or || list,
          or if the command's return status is being inverted using !. 
{code}

I will replace the {{for}} loop with a {{while}} and add a wait before a retry 
as Lars suggested and move everything inside a function that can be reused. 

> Handle curl timeouts better
> ---------------------------
>
>                 Key: WHIRR-207
>                 URL: https://issues.apache.org/jira/browse/WHIRR-207
>             Project: Whirr
>          Issue Type: Bug
>    Affects Versions: 0.3.0
>            Reporter: Lars George
>             Fix For: 0.4.0
>
>
> I have had that happen before and now again. We need to handle this better:
> {code}
> + for i in '`seq 1 3`'
> + curl --retry 3 --silent --show-error --fail -O http://archive.apache.org/dist/hbase/hbase-0.20.6/hbase-0.20.6.tar.gz
> curl: (18) transfer closed with 12646997 bytes remaining to read
> {code}

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message