xpachanges(7) [debian man page]

xpachanges(7)							SAORD Documentation						     xpachanges(7)

NAME

       XPAChanges - Changes For Users from XPA 1.0 and 2.0

SYNOPSIS

       This document describes changes that will affect users who migrate from XPA 1.0 to XPA 2.0.

DESCRIPTION

       There have been a few changes that affect users who upgrade XPA from version 1.0 to version 2.0.  These changes are detailed below.

       o   XPA commands no longer have a resolver routine (this is open to negotiations, but we decided the idea was dumb).  For the SAOtng pro-
	   gram, this means that you must explicitly specify the access point, i.e.,:

	     cat foo.fits | xpaset SAOtng fits

	   instead of:

	     cat foo.fits | xpaset SAOtng

       o   By default, xpaset, xpaget, etc. now wait for the server callback to complete; i.e., the old -W is implied (and the switch is
	   ignored).  This allows support for better error handling.  If you want xpaset, etc.	to return before the callback is complete, use -n
	   switch:

	     echo "file foo.fits" | xpaset -n SAOtng

       o   The old -w switch in xpaset and xpaget is no longer necessary (and is ignored), since you can have more than one process communicating
	   with an xpa access point at one time.

       o   The new -p switch on xpaset means you need not read from stdout:

	     xpaset -p SAOtng colormap I8

	   will send the paramlist to the SAOtng callback without reading from stdin.

SEE ALSO

       See xpa(7) for a list of XPA help pages

version 2.1.14							   June 7, 2012 						     xpachanges(7)

xpausers(7)							SAORD Documentation						       xpausers(7)

NAME

       XPAUsers -  Distinguishing Users

SYNOPSIS

       XPA normally distinguishes between users on a given host, but it is possible to send data to access points belonging to other users.

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.

SEE ALSO

       See xpa(7) for a list of XPA help pages

version 2.1.14							   June 7, 2012 						       xpausers(7)