public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: Simon Xu <xu.simon@oracle.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] xinetd_tests.sh: explicitly enable IPv6
Date: Thu, 30 Jan 2014 05:55:35 -0500 (EST)	[thread overview]
Message-ID: <882926271.1663183.1391079335500.JavaMail.root@redhat.com> (raw)
In-Reply-To: <52DDD0BA.4070906@oracle.com>





----- Original Message -----
> From: "Simon Xu" <xu.simon@oracle.com>
> To: ltp-list@lists.sourceforge.net
> Sent: Tuesday, 21 January, 2014 2:43:22 AM
> Subject: Re: [LTP] [PATCH] xinetd_tests.sh: explicitly enable IPv6
> 
> Could anyone help to review this?
> 
> Thanks
> Simon
> 
> On 2013/12/25 9:43, Simon Xu wrote:
> > Could anyone help to review this?
> >
> > Thanks
> > Simon
> >
> > On 2013/12/11 10:44, Simon Xu wrote:
> >> Explicitly enable IPv6 because on older systems xinetd only listens
> >> on IPv4 by default.
> >>
> >> Signed-off-by: Simon Xu <xu.simon@oracle.com>

Hi,

Looks good to me. According to [1] it's supported since around 1.8.9,
which appears to be older than anything I could find in RHEL distros.

Reviewed-by: Jan Stancek <jstancek@redhat.com>

[1] http://www.tldp.org/HOWTO/Linux%2BIPv6-HOWTO/hints-daemons-xinetd.html

Regards,
Jan

> >> ---
> >>    testcases/network/xinetd/xinetd_tests.sh | 1 +
> >>    1 file changed, 1 insertion(+)
> >>
> >> diff --git a/testcases/network/xinetd/xinetd_tests.sh
> >> b/testcases/network/xinetd/xinetd_tests.sh
> >> index 5024280..dac23a8 100755
> >> --- a/testcases/network/xinetd/xinetd_tests.sh
> >> +++ b/testcases/network/xinetd/xinetd_tests.sh
> >> @@ -134,6 +134,7 @@ service telnet
> >>        server          = /usr/sbin/in.telnetd
> >>        server_args     = -n
> >>        no_access       =
> >> +    flags           = IPv6
> >>    }
> >>    EOF
> >>    RC=$?
> 
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
> 

------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable 
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-01-30 10:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11  2:44 [LTP] [PATCH] xinetd_tests.sh: explicitly enable IPv6 Simon Xu
2013-12-25  1:43 ` Simon Xu
2014-01-21  1:43   ` Simon Xu
2014-01-30 10:55     ` Jan Stancek [this message]
2014-02-10 17:10       ` chrubis

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=882926271.1663183.1391079335500.JavaMail.root@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=xu.simon@oracle.com \
    /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