blob: 4c3353b955e767a4438b52711c8d08ba713d4ba1 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
=pod
=head1 NAME
B<XPAUsers: Distinguishing Users>
=head1 SYNOPSIS
XPA normally distinguishes between users on a given host, but it is possible
to send data to access points belonging to other users.
=head1 DESCRIPTION
A single XPA name service typically serves all users on a given
machine. Two users can register the same XPA access points on the
same machine without conflict, because the user's username is
registered with each access point and, by default, programs such as
xpaget and xpaset only process access points of the appropriate user.
For example:
XPA xpa1 gs 838e2f67:1262 eric
XPA xpa2 gs 838e2f67:1266 eric
XPA xpa1 gs 838e2f67:2523 john
XPA xpa2 gs 838e2f67:2527 john
Here the users "eric" and "john" both have registered the access
points xpa1 and xpa2. When either "john" or "eric" retrieves
information from xpa1, they will process only the access point
registered in their user name.
If you want to access another user's XPA access points on a single
machine, use the -u [user] option on xpaset, xpaget, etc. For example,
if eric executes:
xpaget -u john xpa1
he will access John's xpa1 access point.Use "*" to access all users
on a given machine:
xpaget -u "*" xpa1
Note that the XPA Environment Variable
XPA_NSUSERS can be used to specify the default list of users to
process:
setenv XPA_NSUSERS "eric,john"
will cause access points from both "eric" and "john" to be processed
by default.
=head1 SEE ALSO
See xpa(n) for a list of XPA help pages
=cut
|
