datahub

Transmit all point messages to all registered clients, even if the value does not change.

The maximum message buffer size.

The domain name for this DataHub. This option can be used multiple times to get multiple domains on a single DataHub.

Do not detach from the controlling tty. Normally the DataHub will detach itself and become immune to interrupts and termination on the controlling tty. If this option is used, then an & is necessary to run datahub in the background.

Load this configuration file.

Print a help message showing a summary of all these arguments.

The full path to the directory that will contain the configuration and license files. This takes precedence over -U. If the directory cannot be found or created, the files will be stored in the installation directory.

Log messages to this file.

Acting as a TCP slave, attach to a TCP master on this port or service. The port is the matching port number of the master, usually 4600;

Acting as a TCP slave, attach to a TCP master on this host. The address is a machine name, such as developers.cogentrts.com or a machine address, such as 192.168.3.15.

Acting as a TCP slave, mirror this domain from the TCP master. The named domain on the master will be mirrored to a domain of the same name in the slave.

Act as a TCP master and listen on this port/service.

Specify an alternate queue name for this DataHub. Normally datahub chooses its own queue name to be unique on the network.

Synchronized: The DataHub will ignore changes to a point if the point's current timestamp is more recent.

Automatically generate a timestamp on unstamped points.

The DataHub should NOT create a directory within the user's personal Application Data directory to store the configuration and license files, but rather in the application installation directory. This has a lower precedence than -H.

Generate copious debugging information to the standard output. (Implies use of -D).

Print the version number.

Exit immediately (usually used with -V).