|
Page 644
NAMES A complete name has the syntax family:name where the families are as follows:
The family is case insensitive. The format of the name varies with the family. When Secure RPC is being used, the network-independent netname (for example, nis:unix.uid@domainname) can be specified, or a local user can be specified with just the username and a trailing at sign (@) (for example, nis:pat@). For backward compatibility with pre-R6 xhost, names that contain an at sign are assumed to be in the nis family. Otherwise, the inet family is assumed. DIAGNOSTICS For each name added to the access control list, a line of the form name being added to access control list is printed. For each name removed from the access control list, a line of the form name being removed from access control list is printed. FILES /etc/X*.hosts SEE ALSO X(1), Xsecurity(1), Xserver(1), xdm(1) ENVIRONMENT
BUGS You can't specify a display on the command line because _display is a valid command-line argument (indicating that you want to remove the machine named display from the access list). Page 645 The X server stores network addresses, not hostnames. This is not really a bug. If somehow you change a host's network address while the server is still running, xhost must be used to add the new address and/or remove the old address. AUTHORS Bob Scheifler (MIT Laboratory for Computer Science) and Jim Gettys (MIT Project Athena/DEC) X Version 11 Release 6 xieperfxieperf—XIE server extension test and demo program SYNTAX xieperf [-option ...] DESCRIPTION The xieperf program is based upon R5 x11perf(1) , and while not entirely comprehensive in its coverage of the XIE protocol (see the "Bugs" subsection), it is intended to be useful in the evaluation of XIE implementations in the areas of protocol adherence and performance. The xieperf program includes tests that execute each of the protocol requests and photoflo elements specified by revision 5.0 of the XIE protocol. In addition, xieperf provides a set of tests that can be used to validate the detection and transmission of XIE protocol request errors, such as FloMatch, FloValue, and so forth. Finally, xieperf provides a customizable demonstration program for XIE. A test is made up of three components executed in sequence: an initialization function, a test function, and an end function. The initialization function is responsible for allocating and populating test resources, such as photomaps and LUTs, and for creating a stored photoflo that will be executed by the test function. The test function, in most cases, simply executes the stored photoflo for a specified number of repetitions. The end function, which is called following the test function, is used primarily to destroy any noncacheable server resources used by the test, and to free any memory that was dynamically allocated by the client. Some tests, such as -modify1, -await, -abort, and -redefine, perform additional steps within the test function inner loop, as required by the element being tested, or in an attempt to make the test more visually appealing. Evaluating the performance of individual XIE elements is not as simple as measuring Core X drawing times. The XIE protocol requires elements to be embedded within photoflos in order to be exercised, and the minimum possible photoflo size is two. This implies that it is impossible to measure performance of a single element in isolation—the time it takes to run the flo depends on what other elements exist in the flo. Extrapolating performance of a single element (or technique) in a flo must be done carefully, on a case-by-case basis, because in general, measured element performance depends on input image size, data type, and other factors, all of which can be influenced by upstream flo elements. Note further that the number and type of elements in a flo can be influenced by the visuals available on the display, so even flo-flo comparisons on machines with different visuals must be done with caution. Many test labels contain an abbreviated pipeline description. For instance, IP/IL/P/ED indicates ImportPhotomap, ImportLUT, Point, and ExportDrawable. Pipelines ending in ED (ExportDrawable) often include hidden elements such as BandExtract, ConvertToIndex, Dither, or Point to match the flo output to the screen visual. Pipelines ending in EP (ExportPhotomap) will result in a blank window. xieperf is compatible with x11perfcomp(1), which is used to compare the outputs of different xieperf and x11perf runs in a nice, tabular format. In xieperf you will need to use the -labels option (see the "Options" subsection), and provide the resulting labels file to x11perfcomp(1) to obtain correct output. See the x11perfcomp(1) man pages for more details on this. Page 646 OPTIONS xieperf accepts the following options:
|
