\s-1XPA\s0 normally distinguishes between users on a given host, but it is possible to send data to access points belonging to other users.
A single \s-1XPA\s0 name service typically serves all users on a given machine. Two users can register the same \s-1XPA\s0 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 \*(L"eric\*(R" and \*(L"john\*(R" both have registered the access points xpa1 and xpa2. When either \*(L"john\*(R" or \*(L"eric\*(R" retrieves information from xpa1, they will process only the access point registered in their user name.
If you want to access another user's \s-1XPA\s0 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 \*(L"*\*(R" to access all users on a given machine:
xpaget \-u "*" xpa1
Note that the \s-1XPA\s0 Environment Variable \s-1XPA_NSUSERS\s0 can be used to specify the default list of users to process:
setenv XPA_NSUSERS "eric,john"
will cause access points from both \*(L"eric\*(R" and \*(L"john\*(R" to be processed by default.
See xpa(7) for a list of \s-1XPA\s0 help pages