On Thu, 2008-12-18 at 14:34 +0900, Mitsuru Chinen wrote: > On Thu, 18 Dec 2008 10:49:22 +0530 > Sudhir Kumar <[email protected]> wrote: > > > > + When you would like to run the same tests which networktests.sh ran > > > till > > > + 2008, specify no option or -d option: > > How can one come to know what tests were run till 2008? A small > > description of tests would be better here.
I do not see Sudhir´s discussion´s on the mailing lists. Can you route all the queries through this list ?? > > You got a point there. How about this? > > | Up to 2008, networktests.sh ran the tests written in multicast, nfs, rpc > | and tcp_cmds command files. When you would like to run those tests, > specify > | no option or -d option: > | # ./networktests.sh > > Here's the revised patch: The earlier has already been applied. Regards-- Subrata > > === > > [PATCH] Update the description of networktests.sh > > The description of the networktests.sh in INTALL file is a bit old. > This patch adds the description regarding PAM and test menu. > > Signed-off-by: Mitsuru Chinen <[email protected]> > --- > INSTALL | 39 +++++++++++++++++++++++++++++---------- > 1 files changed, 29 insertions(+), 10 deletions(-) > > diff --git a/INSTALL b/INSTALL > index d7d49d8..b07bf24 100644 > --- a/INSTALL > +++ b/INSTALL > @@ -78,10 +78,18 @@ contributions are welcome. > the LTP on this server machine also. > > ii) Second, the server must be setup to allow the client to connect using > - the "r" commands, such as rsh. This is done by simply > creating/editing > - the ".rhosts" file under /root. Place the hostname of the > client > - machine in this file to allow root to remotely connect without > the use > - of a password. > + the "r" commands, such as rsh. This is done by simply creating/editing > + the ".rhosts" file under /root. Place the hostname of the client > + machine in this file to allow root to remotely connect without the use > + of a password. If server has the PAM system security tool, you need > + to add the following lines to /etc/securetty: > + rlogin > + rsh > + rexec > + pts/0 > + pts/1 > + : > + pts/9 > > iii) Next, certain services must be activated in order for certain tests > to > execute. The following services are activated via inetd/xinetd: > @@ -91,13 +99,24 @@ contributions are welcome. > echo (stream) > fingerd > rshd > - Also, because certain RPC programs are tested, the > "portmapper" daemon > - MUST be started, as well as NFS server AND lock services. > + Also, because certain RPC programs are tested, the "portmapper" daemon > + MUST be started, as well as NFS server AND lock services. > > iv) Finally, before running the networktests.sh script, two variables > must > - be set within the script file. The "RHOST" variable should be > set to > - the hostname of the server. The "PASSWD" variable should be > set to > - root's password on the server machine. This is necessary for > tests > - such as telnet01 and ftp01. > + be set within the script file. The "RHOST" variable should be set to > + the hostname of the server. The "PASSWD" variable should be set to > + root's password on the server machine. This is necessary for tests > + such as telnet01 and ftp01. > > You can now successfully execute the networktests.sh script. > + When you would like to run the whole network tests, specify -w option: > + # ./networktests.sh -w > + > + Up to 2008, networktests.sh ran the tests written in multicast, nfs, rpc > + and tcp_cmds command files. When you would like to run those tests, > specify > + no option or -d option: > + # ./networktests.sh > + > + You can run the test category which you are interested in, -h option shows > + the list of the test category: > + # ./netwoktests.sh -h ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
