![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to README CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / sys / nfs / TEST / billboard|
Return to README CVS log | Up to [CSRG BSD Unix] / 43BSDReno / sys / nfs / TEST / billboard |
1.1 root 1: Product Description:
2: -------------------
3: The BillBoard is an RPC service program which maintains
4: the information about testsuite completions. There are 2 parts to the
5: program, the client and the server. The client provides an interface
6: with which the user may update or view testsuite completions. The
7: server maintains all data input by the client.
8: In order for a client to access or modify any data on the server
9: it must be supplied with an identifier. The server uses this
10: identifier as a key for data access. The identifiers will be assigned
11: by Sun and will be issued at Connectathon. For the purpose of testing
12: the billboard programs on your machine, you use the identifiers
13: which you specify in the bb_data.company file. An example data file
14: is provided for you and includes a description of the file. A
15: password may be set for each identifier to provide some measure of
16: security.
17:
18: There are 2 versions of the program:
19: billboard and bb are the client and server program respectively for
20: the NFS testsuites.
21:
22: xbillboard and xbb are the client and server program respectively for
23: the X testsuites.
24:
25:
26: Usage:
27: -----
28: Client:
29: ------
30: 1) Set the environment variable BB_SERVER to the hostname of the
31: machine running the billboard server,
32: eg. If we are using the billboard programs for the NFS testsuites
33: and the host running bb server is "holy_cow", then you may
34: do this
35: %setenv BB_SERVER holy_cow
36:
37: 2) Run the client program:
38: for the NFS testsuites:
39: billboard [-s|-u client_identifier server_identifier]
40: [-a|-b client_identifier]
41: [-c|-d server_identifier]
42: [-p identifier]
43:
44: for the X testsuites:
45: xbillboard [-s|-u client_identifier server_identifier]
46: [-a|-b client_identifier]
47: [-c|-d server_identifier]
48: [-p identifier]
49:
50: options:
51: -s client_identifier server_identifier>
52: is to set test between client_identifier and
53: server_identifier as successfully tested
54: -u client_identifier server_identifier
55: to set test between client_identifier and
56: server_identifier as NOT successfully tested
57: -a client_identifier
58: to list server implementations that are successfully
59: tested against client client_identifier
60: -b client_identifier
61: to list server implementations that are NOT
62: successfully tested against client client_identifier
63: -c server_identifier
64: to list client implementations that are successfully
65: tested against server server_identifier
66: -d server_identifier
67: to list client implementations that are NOT
68: successfully tested against server server_identifier
69: -p identifier
70: to change the password of the identifier implementation.
71: There is a password for each implementation.
72:
73: where
74: client_identifier and server_identifier are
75: identifiers of the client and server implementation
76: respectively.
77:
78: If no option is specified, the program is in interactive mode.
79: Whereby the user is presented with a list of options
80: (same as the features described above) to choose from.
81: User will be prompted for any additional data.
82:
83: Server:
84: -------
85: 1) In order to use the billboard server you must edit the file
86: named bb_data.company. This file contains entries for each
87: implementation to be tested. The file itself contains information
88: about it's structure and syntax.
89:
90: 2) Start the billboard server from the same directory where the
91: bb_data.company file exists. The name of the executable is bb for
92: NFS testsuite server, and xbb for X testsuite server.
93:
94:
95: Porting Note:
96: ------------
97: The current implementation runs on all Sun platforms.
98: You will need to port the client programs, (i.e. billboard if you are testing
99: NFS at Connectathon, and xbillboard if you are testing X).
100: Though, you do need to port the servers to your machine to test the client
101: programs, both servers will be provided and run on a Sun machine at
102: Connectathon.
103:
104: All sources are in the src/ directory.
105: Sources for client program uses "billboard" as prefix, and server use
106: "bb" as prefix. The Makefile contains compilation instructions for both
107: client and servers. protocol.x is the the protocol to be used with rpcgen.
108:
109: To compile:
110: %cd src
111: %make makes client and server executables, OR
112: %make debug makes with -g option
113:
114: What can be modified:
115: --------------------
116: 1) At Connectathon the billboard servers will be run ONLY on a Sun machine,
117: hence, only the client program may be modified to your liking.
118:
119: 2) The password encryption algorithm can be modified in _bb_get_passwd()
120: (billboard.c). The algorithm used is UNIX DES with a fixed salt key, you
121: are welcome to implement your own.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.