public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Simon Xu <xu.simon@oracle.com>
To: Mike Frysinger <vapier@gentoo.org>, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] ip_tests.sh: don't use hardcoded eth0
Date: Wed, 09 Apr 2014 14:09:49 +0800	[thread overview]
Message-ID: <5344E42D.9050801@oracle.com> (raw)
In-Reply-To: <698021823.mA9edKhrul@vapier>

In my CentOS box, running "ifconfig lo:1 10.1.1.12" immediately hangs 
the ssh connection, I have to run "systemctl restart network" in local 
tty to make network work again.  Could you help to try the testcases in 
ip_tests.sh on your box and report back?

Thanks
Simon

On 2014/3/28 13:08, Mike Frysinger wrote:
> On Fri 28 Mar 2014 09:44:24 Simon Xu wrote:
>> The script uses hardcoded 'eth0' which used to work on most systems.
>> This fix tries to find a 'working' network interface using the hostname.
> why doesn't hardcoding "lo" work ?
> -mike


------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-04-09  6:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28  1:44 [LTP] [PATCH] ip_tests.sh: don't use hardcoded eth0 Simon Xu
2014-03-28  5:08 ` Mike Frysinger
2014-04-09  6:09   ` Simon Xu [this message]
2014-04-25 12:04   ` Stanislav Kholmanskikh
2014-04-09  6:10 ` Simon Xu
2014-04-25  1:06 ` Simon Xu
2014-04-25 12:26 ` Stanislav Kholmanskikh
  -- strict thread matches above, loose matches on Subject: below --
2014-04-25 13:59 Joseph Beckenbach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5344E42D.9050801@oracle.com \
    --to=xu.simon@oracle.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox