acslist(1) [debian man page]

ACSLIST(1)							  BP executables							ACSLIST(1)

NAME

       acslist - Aggregate Custody Signals (ACS) utility for checking custody IDs.

SYNOPSIS

       acslist [-s|--stdout]

DESCRIPTION

       acslist is a utility program that lists all mappings from bundle ID to custody ID currently in the local bundle agent's ACS ID database, in
       no specific order.  A bundle ID (defined in RFC5050) is the tuple of (source EID, creation time, creation count, fragment offset, fragment
       length).  A custody ID (defined in draft-jenkins-aggregate-custody-signals) is an integer that the local bundle agent will be able to map
       to a bundle ID for the purposes of aggregating and compressing custody signals.

       The format for mappings is:

       (ipn:13.1,333823688,95,0,0)->(26)

       While listing, acslist also checks the custody ID database for self-consistency, and if it detects any errors it will print a line starting
       with "Mismatch:" and describing the error.

       -s|--stdout tells acslist to print results to stdout, rather than to the ION log.

EXIT STATUS

       0   acslist terminated after verifying the consistency of the custody ID database.

       1   acslist was unable to attach to the ACS database, or it detected an inconsistency.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

       The following diagnostics may be issued:

       Can't attach to ACS.
	   acsadmin has not yet initialized ACS operations.

       Mismatch: (description of the mismatch)
	   acslist detected an inconsistency in the database; this is a bug in ACS.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       acsadmin(1), bplist(1)

perl v5.14.2							    2012-05-25								ACSLIST(1)

ACSADMIN(1)							  BP executables						       ACSADMIN(1)

NAME

       acsadmin - ION Aggregate Custody Signal (ACS) administration interface

SYNOPSIS

       acsadmin [ commands_filename ]

DESCRIPTION

       acsadmin configures aggregate custody signal behavior for the local ION node.

       It operates in response to ACS configuration commands found in the file commands_filename, if provided; if not, acsadmin prints a simple
       prompt (:) so that the user may type commands directly into standard input.

       The format of commands for commands_filename can be queried from acsadmin with the 'h' or '?' commands at the prompt.  The commands are
       documented in acsrc(5).

EXIT STATUS

       0 Successful completion of ACS administration.

EXAMPLES

       acsadmin
	   Enter interactive ACS configuration command entry mode.

       acsadmin host1.acs
	   Execute all configuration commands in host1.acs, then terminate immediately.

FILES

       See acsrc(5) for details of the ACS configuration commands.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

       Note: all ION administration utilities expect source file input to be lines of ASCII text that are NL-delimited.  If you edit the acsrc
       file on a Windows machine, be sure to use dos2unix to convert it to Unix text format before presenting it to acsadmin.  Otherwise acsadmin
       will detect syntax errors and will not function satisfactorily.

       The following diagnostics may be issued to the logfile ion.log:

       acsadmin can't attach to ION.
	   There is no SDR data store for acsadmin to use.  You should run ionadmin(1) first, to set up an SDR data store for ION.

       Can't open command file...
	   The commands_filename specified in the command line doesn't exist.

       Various errors that don't cause acsadmin to fail but are noted in the ion.log log file may be caused by improperly formatted commands given
       at the prompt or in the commands_filename file.	Please see acsrc(5) for details.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       ionadmin(1), bpadmin(1), acsrc(5)

perl v5.14.2							    2012-05-25							       ACSADMIN(1)