[netperf-talk] naming and/or locations

[Yun, James K]

I would keep netperf2 as netperf since that is the current default
version. Changing it to netperf2 may cause confusions or hassles for
users.

I would thus install netperf4 as netperf4 to delineate it as a different
version that is available for users that want it. If netperf4 is a true
superset of netperf2 (i.e., it can be set to function exactly like
netperf2), then eventually you may want to consider replacing netperf2
with netperf4 if enough users are comfortable with it.

James

-----Original Message-----
From: netperf-talk-bounces at netperf.org
[mailto:netperf-talk-bounces at netperf.org] On Behalf Of Rick Jones
Sent: Wednesday, March 01, 2006 12:11 PM
To: netperf-talk at netperf.org
Subject: Re: [netperf-talk] naming and/or locations

> Another thought, if both netperf2 and netperf4 use the same port,
> it will muck up auto starting the correct netserver version via
> inetd.  I haven't looked, just guessing that this may be another
> issue if both versions are installed...

That one is already covered.  The default port number for the netperf4 
control connection is different from that for netperf2.  Netperf2 uses 
12865, netperf4 uses 56821.

> I think it isn't needed to append a 2 or 4 to the binary. Because, you
> should leave that decision to the administrator. He decides which
> package to install and use. So, what is the benefit of installing both
> v2 and v4 of netperf at the same time?

Netperf v2 is rather simpler and for just plain pt-pt performance 
measurements may make more sense than netperf4, which has all the 
overheads associated with multiple, synchronized connections.

What would be the "GNU/autoconf/whatever" way of dealing with multiple 
revisions of a package on the same system?

rick jones
_______________________________________________
netperf-talk mailing list
netperf-talk at netperf.org
http://www.netperf.org/cgi-bin/mailman/listinfo/netperf-talk