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. 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 > > > Jan Karlsson > Senior Software Engineer > MIB > > Sony Mobile Communications > Tel: +46703062174 > sonymobile.com > > > > -----Original Message----- > From: crash-utility-bounces@xxxxxxxxxx [mailto:crash-utility-bounces@xxxxxxxxxx] On Behalf Of Dave Anderson > Sent: onsdag den 18 juli 2012 15:19 > To: Discussion list for crash utility usage, maintenance and development > Subject: Re: timeout in eppic.mk > > > > ----- Original Message ----- >> Thanks Dave, the patch works as intended for me. I now get a 10 sec >> timeout instead of the 10 min timeout I had before, followed by the >> message "failed to pull epic code .....". > > Right, although I'm surprised that you have a 10 second timeout. > > If I put in a valid name of a machine that I've shut down, the "ping -c 1 <name>" only takes about 1 second to return a failure. > > Anyway, I'll queue that change for crash-6.0.9. > > Thanks, > Dave > > > -- > Crash-utility mailing list > Crash-utility@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/crash-utility > > -- > Crash-utility mailing list > Crash-utility@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/crash-utility -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
