Campbell Scientific LoggerNet for Linux Installation Guide - Manual (Page 9)

LoggerNet for Linux Installation Guide
any firewall on the LoggerNet server PC or on the network between the remote
client PC and the LoggerNet server PC.
You should read the installation guide for your distribution of Linux to
understand the firewall application and how to grant or deny access for the
LoggerNet server TCP port.
Once remote TCP connections to the LoggerNet server are allowed through the
firewall, the LoggerNet Remote Windows clients can access the LoggerNet
server on Linux by specifying the IP address or qualified domain name of the
LoggerNet server PC. If you don't know the IP address of your Linux PC, the
"ifconfig" command issued in a terminal window will display the IP address
and properties of the network interface.
By default, security is disabled in the LoggerNet server, which
means all LoggerNet Remote clients can access the LoggerNet
server with full administrator rights. If security is a concern, use
the Security Manager client in LoggerNet Remote to enable
security in the LoggerNet server. For more information, read the
section about the Security Manager in the LoggerNet manual. NOTE
4.3 Command Line Options
Advanced Linux administrators may have reasons to modify the provided init
scripts, create their own, or use other methods for launching the daemon. The
csilgrnet executable supports the following command line options:
--IpPort=xxxx: Specifies the TCP port to which the server will be bound.
--WorkDir=path: Specifies the directory where the server will store its
working directory (usually in sys/bin relative to the AppDir).
--AppDir=path: Specifies the directory where the server will write, by
default, such things as data files.
--IpBindAddress=aaa.bbb.ccc.ddd: Specifies the address of the interface to
which the server will be bound. If empty, the server will bind to all
available interfaces.
--logFileDir=path: Specifies the directory where the server will write its
log files.
--run-as-daemon=<true|false>: Specifies whether the program should run
as a daemon. When true, this will force the program to fork, set the
umask, call setsid(), and to detach its I/O handles.
4.4 Configuring the Export Daemons (LDMP and LDEP)
The LoggerNet data export daemons, LDMP and LDEP, are described in
Section 1.3, Logger Data Monitor Protocol Server (LDMP), and Section 1.4,
Logger Data Export Protocol Server (LDEP).
5