diff --git a/doc/tutorial/source/getting-started.rst b/doc/tutorial/source/getting-started.rst index 80c5d7874..567b2227b 100644 --- a/doc/tutorial/source/getting-started.rst +++ b/doc/tutorial/source/getting-started.rst @@ -1429,7 +1429,7 @@ For example, to run your |ns3| program ``hello-simulator`` with the arguments .. sourcecode:: console - $ ./ns3 run=hello-simulator --command-template="gdb %s --args " + $ ./ns3 run hello-simulator --command-template="gdb %s --args " Notice that the |ns3| program name goes with the ``--run`` argument, and the control utility (here ``gdb``) is the first token diff --git a/examples/tcp/tcp-star-server.cc b/examples/tcp/tcp-star-server.cc index 6691a2d7f..146d61499 100644 --- a/examples/tcp/tcp-star-server.cc +++ b/examples/tcp/tcp-star-server.cc @@ -33,10 +33,10 @@ // "tcp-star-server-$n-$i.pcap" where n and i represent node and interface // numbers respectively // Usage examples for things you might want to tweak: -// ./ns3 run="tcp-star-server" -// ./ns3 run="tcp-star-server --nNodes=25" -// ./ns3 run="tcp-star-server --ns3::OnOffApplication::DataRate=10000" -// ./ns3 run="tcp-star-server --ns3::OnOffApplication::PacketSize=500" +// ./ns3 run "tcp-star-server" +// ./ns3 run "tcp-star-server --nNodes=25" +// ./ns3 run "tcp-star-server --ns3::OnOffApplication::DataRate=10000" +// ./ns3 run "tcp-star-server --ns3::OnOffApplication::PacketSize=500" // See the ns-3 tutorial for more info on the command line: // http://www.nsnam.org/tutorials.html diff --git a/src/core/examples/hash-example.cc b/src/core/examples/hash-example.cc index cfdbcb0bc..537908a2e 100644 --- a/src/core/examples/hash-example.cc +++ b/src/core/examples/hash-example.cc @@ -40,7 +40,7 @@ * Example Output: * \verbatim -./ns3 run="hasher-example --time \ +./ns3 run "hasher-example --time \ --dict=/usr/share/dict/web2 \ --dict=/usr/share/dict/web2a \ --dict=/usr/share/dict/propernames \ diff --git a/src/core/model/command-line.h b/src/core/model/command-line.h index 1c412acca..97015719f 100644 --- a/src/core/model/command-line.h +++ b/src/core/model/command-line.h @@ -156,19 +156,19 @@ namespace ns3 { * Here is the output from a few runs of that program: * * \verbatim - $ ./ns3 run="command-line-example" + $ ./ns3 run "command-line-example" intArg: 1 boolArg: false strArg: "strArg default" cbArg: "cbArg default" - $ ./ns3 run="command-line-example --intArg=2 --boolArg --strArg=Hello --cbArg=World" + $ ./ns3 run "command-line-example --intArg=2 --boolArg --strArg=Hello --cbArg=World" intArg: 2 boolArg: true strArg: "Hello" cbArg: "World" - $ ./ns3 run="command-line-example --help" + $ ./ns3 run "command-line-example --help" ns3-dev-command-line-example-debug [Program Arguments] [General Arguments] CommandLine example program. diff --git a/src/fd-net-device/examples/fd-emu-onoff.cc b/src/fd-net-device/examples/fd-emu-onoff.cc index fc3e7d6f0..ed119c4f6 100644 --- a/src/fd-net-device/examples/fd-emu-onoff.cc +++ b/src/fd-net-device/examples/fd-emu-onoff.cc @@ -96,11 +96,11 @@ // // 6 - Run the server side: // -// server host: $ ./ns3 run="fd-emu-onoff --serverMode=1" +// server host: $ ./ns3 run "fd-emu-onoff --serverMode=1" // // 7 - Run the client side: // -// client host: $ ./ns3 run="fd-emu-onoff" +// client host: $ ./ns3 run "fd-emu-onoff" // #include diff --git a/src/fd-net-device/examples/fd2fd-onoff.cc b/src/fd-net-device/examples/fd2fd-onoff.cc index 9d6a42cb4..92840c91e 100644 --- a/src/fd-net-device/examples/fd2fd-onoff.cc +++ b/src/fd-net-device/examples/fd2fd-onoff.cc @@ -37,8 +37,8 @@ // // Steps to run the experiment: // -// $ ./ns3 run="fd2fd-onoff" -// $ ./ns3 run="fd2fd-onoff --tcpMode=1" +// $ ./ns3 run "fd2fd-onoff" +// $ ./ns3 run "fd2fd-onoff --tcpMode=1" // #include diff --git a/src/fd-net-device/examples/realtime-fd2fd-onoff.cc b/src/fd-net-device/examples/realtime-fd2fd-onoff.cc index 880e92004..92e307c3f 100644 --- a/src/fd-net-device/examples/realtime-fd2fd-onoff.cc +++ b/src/fd-net-device/examples/realtime-fd2fd-onoff.cc @@ -37,7 +37,7 @@ // // Steps to run the experiment: // -// $ ./ns3 run="fd2fd-onoff" +// $ ./ns3 run "fd2fd-onoff" // #include diff --git a/src/lte/doc/source/lte-user.rst b/src/lte/doc/source/lte-user.rst index b9e08b484..f2961be89 100644 --- a/src/lte/doc/source/lte-user.rst +++ b/src/lte/doc/source/lte-user.rst @@ -2188,7 +2188,7 @@ appending the parameters and their values to the ``ns3`` call when starting each individual simulation. So the ``ns3`` calls for invoking our 3 simulations would look as below:: - $ ./ns3 run="lena-dual-stripe + $ ./ns3 run "lena-dual-stripe --simTime=50 --nBlocks=0 --nMacroEnbSites=7 --nMacroEnbSitesX=2 --epc=1 --useUdp=0 --outdoorUeMinSpeed=16.6667 --outdoorUeMaxSpeed=16.6667 --ns3::LteHelper::HandoverAlgorithm=ns3::NoOpHandoverAlgorithm @@ -2198,7 +2198,7 @@ look as below:: --ns3::PhyStatsCalculator::UlSinrFilename=no-op-UlSinrStats.txt --RngRun=1" > no-op.txt - $ ./ns3 run="lena-dual-stripe + $ ./ns3 run "lena-dual-stripe --simTime=50 --nBlocks=0 --nMacroEnbSites=7 --nMacroEnbSitesX=2 --epc=1 --useUdp=0 --outdoorUeMinSpeed=16.6667 --outdoorUeMaxSpeed=16.6667 --ns3::LteHelper::HandoverAlgorithm=ns3::A3RsrpHandoverAlgorithm @@ -2208,7 +2208,7 @@ look as below:: --ns3::PhyStatsCalculator::UlSinrFilename=a3-rsrp-UlSinrStats.txt --RngRun=1" > a3-rsrp.txt - $ ./ns3 run="lena-dual-stripe + $ ./ns3 run "lena-dual-stripe --simTime=50 --nBlocks=0 --nMacroEnbSites=7 --nMacroEnbSitesX=2 --epc=1 --useUdp=0 --outdoorUeMinSpeed=16.6667 --outdoorUeMaxSpeed=16.6667 --ns3::LteHelper::HandoverAlgorithm=ns3::A2A4RsrqHandoverAlgorithm @@ -2415,7 +2415,7 @@ along entire system bandwidth. User needs to specify FR algorithm by overriding the default attribute ``ns3::LteHelper::FfrAlgorithm``. Example command to run ``lena-dual-stripe`` with Hard FR algorithm is presented below:: - $ ./ns3 run="lena-dual-stripe + $ ./ns3 run "lena-dual-stripe --simTime=50 --nBlocks=0 --nMacroEnbSites=7 --nMacroEnbSitesX=2 --epc=1 --useUdp=0 --outdoorUeMinSpeed=16.6667 --outdoorUeMaxSpeed=16.6667 --ns3::LteHelper::HandoverAlgorithm=ns3::NoOpHandoverAlgorithm @@ -2429,7 +2429,7 @@ Example command to run ``lena-dual-stripe`` with Hard FR algorithm is presented Example command to generate REM for RB 1 in data channel from ``lena-dual-stripe`` scenario with Hard FR algorithm is presented below:: - $ ./ns3 run="lena-dual-stripe + $ ./ns3 run "lena-dual-stripe --simTime=50 --nBlocks=0 --nMacroEnbSites=7 --nMacroEnbSitesX=2 --epc=0 --useUdp=0 --outdoorUeMinSpeed=16.6667 --outdoorUeMaxSpeed=16.6667 --ns3::LteHelper::HandoverAlgorithm=ns3::NoOpHandoverAlgorithm diff --git a/src/tap-bridge/examples/tap-csma-virtual-machine.cc b/src/tap-bridge/examples/tap-csma-virtual-machine.cc index 19ea1f178..f7c484cac 100644 --- a/src/tap-bridge/examples/tap-csma-virtual-machine.cc +++ b/src/tap-bridge/examples/tap-csma-virtual-machine.cc @@ -97,7 +97,7 @@ main (int argc, char *argv[]) // devices installed on both of the nodes. The data rate and delay for the // channel can be set through the command-line parser. For example, // - // ./ns3 run "tap=csma-virtual-machine --ns3::CsmaChannel::DataRate=10000000" + // ./ns3 run "tap-csma-virtual-machine --ns3::CsmaChannel::DataRate=10000000" // CsmaHelper csma; NetDeviceContainer devices = csma.Install (nodes);