ramsgate - Online in the Cloud

PROGRAM:

NAME

ramsgate - Remote AMS gateway daemon

SYNOPSIS

ramsgate application_name authority_name [bundles_TTL]

DESCRIPTION

ramsgate is a background "daemon" task that functions as a Remote AMS gateway.
application_name and authority_name must identify an AMS venture that is known to operate
in the local continuum, as noted in the MIB for the ramsgate application module.

ramsgate will register as an application module in the root unit of the indicated venture,
so a configuration server for the local continuum and a registrar for the root unit of the
indicated venture (which may both be instantiated in a single amsd daemon task) must be
running in order for ramsgate to commence operations.

ramsgate with communicate with other RAMS gateway modules in other continua by means of
the RAMS network protocol noted in the RAMS gateway endpoint ID for the local continuum,
as identified (explicitly or implicitly) in the MIB.

If the RAMS network protocol is "bp" (i.e., the DTN Bundle Protocol), then an ION Bundle
Protocol node must be operating on the local computer and that node must be registered in
the BP endpoint identified by the RAMS gateway endpoint ID for the local continuum.
Moreover, in this case the value of bundles_TTL - if specified - will be taken as the
lifetime in seconds that is to be declared for all "bundles" issued by ramsgate;
bundles_TTL defaults to 86400 seconds (one day) if omitted.

EXIT STATUS

"0" ramsgate terminated normally.

"1" ramsgate failed, for reasons noted in the ion.log file; the task terminated.

Use ramsgate online using onworks.net services