----- Original Message ----- > Different network topologies/setups will have different failure modes. > If you want to dig into this I would suggest getting a network capture > (tcpdump -s0) at the time of the problem so we can see exactly at what > level it is timing out. That said I am not sure the crash build > scripts should really have to deal with this kind of things. Right -- I think I'll just leave it as is (i.e. without -W), and let it timeout based upon the host machine's setup. It's not that big a deal, and Jan was happy enough with his 10-second timeout vs. the annoying 10-minute git command timeout. Dave > On Thu, Jul 19, 2012 at 6:40 AM, Karlsson, Jan > <Jan.Karlsson@xxxxxxxxxxxxxx> wrote: > > Hi > > > > I searched for information on this and it seems that the timeout is > > dependent on Linux installation. 10 sec seems also to be a not > > uncommon default timeout. If you want to set the timeout you can > > use the -W option. > > > > ping -c 1 -W 1 code.google.com > > > > will timeout after 1 sec for me. > > > > Jan -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility