/* 
* Copyright (c) 2001 by Sun Microsystems, Inc.
# All rights reserved.
#
*/ 

TEST NAME 

      lsalr - test network load bearing

SYNOPSIS 

      sh lsalr.sh REMOTE-MACHINE INSTANCES ITERATIONS

DESCRIPTION 

      This test initiates several simultaneous directory-listing processes on a
      remote machine to test network load bearing.

      This test initiates several remote 'ls -alR' commands that run
      concurrently in the background.

OPERANDS 

       REMOTE-MACHINE  Either the host name or IP address of the machine to
                       which files and directories are copied. If the host
                       name is given, it must appear in /etc/hosts along
                       with the remote machine's IP address.

       INSTANCES       Number of concurrent 'ls -alR' processes to run. This
                       number is machine-dependent, but typically you can
                       run 10 to 15 processes for 100 percent CPU utilization
                       on a 350 MHz Pentium with 32 Mbytes of RAM.

       ITERATIONS      Number of times to rerun the test.

SETUP 

      You need two machines connected by a network, either back-to-back, or
      through a hub or switch.

OUTPUT 

      This test indicates its progress before and after each test iteration,
      and ends by displaying the total time the test ran.

DURATION 

      24 hours

POSSIBLE CONCURRENT TESTS 

      * This test is usually run alongside a second test to further stress the
        driver/NIC.

      * The runtime period should be judged so as to run for as long as the
        concurrent tests are running, but if run independently, then 24 hours
        is sufficient.

      * This test can run concurrently with cl3se3, ftptest, mpflip, and spray.

NOTES 

      This test might cause a problem if it runs too quickly, in that it
      consumes all available sockets. After a socket is closed, the socket
      stays in the TIME_WAIT state for up to 2 minutes, during which it cannot
      be reused. For this reason, the test alters the tcp_time_wait_interval 
      to a lower value as it runs.

EXAMPLES 

      $ lsalr.sh yorke 10 3

      Iteration #3

      Running 10 instance(s) of test on yorke:Done

      Iteration #2

      Running 10 instance(s) of test on yorke:Done

      Iteration #1

      Running 10 instance(s) of test on yorke:Done

      Started at   : Tue Jun 22 12:16:06 BST 1999
      Completed at : Tue Jun 22 12:45:17 BST 1999
      All processes completed.
      $

REFERENCES 

      ls(1), ssh(1), hosts(4)
