1. 28 Mar, 2002 3 commits
  2. 27 Mar, 2002 7 commits
  3. 26 Mar, 2002 4 commits
  4. 25 Mar, 2002 16 commits
  5. 24 Mar, 2002 1 commit
  6. 22 Mar, 2002 9 commits
    • Leigh Stoller's avatar
      Oops, never change this file by hand! · d31bdf85
      Leigh Stoller authored
      d31bdf85
    • Leigh Stoller's avatar
      Add code to the parser to populate a new virt_agents table, which · 2917542a
      Leigh Stoller authored
      provides a mapping from an object ($cbr0) to the node on which the
      agent is running ($nodeA). It also includes the type of agent
      (TRAFGEN, LINK, etc). There were a number of reasons for adding this
      table:
      
      * To avoid a series of specialized table lookups in the event
        scheduler to map from a name (link0) to the node on which the agent
        is running. Previously, it was looking the delays table and the
        virt_trafgens table. Well, now it just needs to look at this one
        table and store the mapping internally. When a dynamic event comes
        in, we can figure out where to send it easily.
      
      * For NSE traffic generation. Unlike the simple TG based CBRs, Shashi
        wants to be able to send events to any of the objects in the config
        (udp0, telnet0, ftp0, etc). Well, the virt_trafgens table certainly
        does not store that info, and it would have been painful to work
        this into it. For every agent/application, just add an entry in the
        virt_agents table and the scheduler knows where to send the events.
      
      * It nicely supports the new program object; just plug an entry in the
        virt_agents table.
      
      Okay, there is one messy aspect; delays nodes! Delay nodes are not
      computed until after assign wrapper runs, so in addition to munging
      the static event list in assign_wrapper, we now munge the virt_agents
      table as well. Not much to do about this; delay nodes are handled
      outside the normal path everywhere.
      2917542a
    • Leigh Stoller's avatar
      Add -f (force) option to start a scheduler even when no static events. · f7024783
      Leigh Stoller authored
      Note, this is going to change soon when we make dynamic events real;
      will need to start a scheduler with every experiment.
      f7024783
    • Leigh Stoller's avatar
      Add client side support to run the new program agent on both linux and · e4e77091
      Leigh Stoller authored
      freebsd. No biggie, just some minor script changes.
      e4e77091
    • Leigh Stoller's avatar
      Add new NS program object. This syntax is different than I had · b9ba3398
      Leigh Stoller authored
      originally anticipated, but I was worried about confusion with the
      Agent/Application API that NS provides, and which is substantially
      different than this. Anyway, I added support for this syntax:
      
      	set prog0 [$ns program]
      	$prog0 set node $nodeA
      	$prog0 set command "/bin/ls -lt >& /users/stoller/logs/foo"
      
      Kinda obvious, although whats not obvious is that without events to
      start and stop them, these will never run. So, I added support for
      this:
      
      	$ns at 10 "$prog0 start"
      	$ns at 20 "$prog0 stop"
      
      You can start and stop programs as much as you like, but you cannot
      start a program that is already running; you have to stop it first.
      You can also issue these dynamically using the same api:
      
      	tevc -e testbed/Tevents now prog0 start \
      		"command=/bin/ls -lt / >& /users/stoller/logs/foo"
      	tevc -e testbed/Tevents now prog0 stop
      
      Note the quotes when using a multiword command. I also had intened to
      support a KILL command so that you could send arbitrary signals to a
      process. I added that, but I will not bother to document it yet; since
      I invoke /bin/csh to process the command line, the issue of signals is
      a little fuzzy. Sending a signal like -HUP to the parent process (the
      csh) is not really what we want to do. I think we can support this,
      but I need to poke around and see what the right way is.
      b9ba3398
    • Leigh Stoller's avatar
      Add PROGRAM and KILL object/events. · 340fda00
      Leigh Stoller authored
      340fda00
    • Leigh Stoller's avatar
      New "program agent" that runs on the client nodes (freebsd and linux) · 187a3a18
      Leigh Stoller authored
      and reponds to PROGRAM events. Currently, just start and stop. Start
      takes a COMMAND= argument, and allows arbitrary command lines since I
      pass the whole thing off to the shell. Caveat; the agent runs as root
      and starts the program as root. You can has as many program objects in
      your NS file as you like, but each one can be started once; you have
      to either stop or wait for the old one to finish before trying to
      start again.
      187a3a18
    • Leigh Stoller's avatar
      Change to remove the entire sup checkouts tree on the client node; · b0c42f89
      Leigh Stoller authored
      prepare was failing to remove that directory on the older images cause
      prepare was hardwired to the current release name.
      b0c42f89
    • Leigh Stoller's avatar
      Minor fix to shipset.awk call; place result in quotes so the shell · 05222bfc
      Leigh Stoller authored
      does not wigged out by the ?? return value.
      05222bfc