1.9 Running the gator daemon on your target
When all of the necessary files are in place, you can start
gatord, the gator daemon.
gatord needs to be actively running for Streamline to initiate a capture session over Ethernet or USB. This setup task applies to both Linux and Android targets.
NoteYou can install and run user space gator on the target automatically by
clicking the Setup target... button in the
Connection Browser dialog.
gatord manually, follow these
gatord and, optionally, gator.ko into the file system on the target. On
Android, you can do this on your host using adb
gatord has execute permission, enter the
On Android, you can execute this command using adb
gatord is in a different directory to
gator.ko on the target, you must do one of the
gatord does not exist in the same
directory as gator.ko and you do not
either manually insert gator.ko or
include a path to it when running
user-space only version of
gatord runs when
the command is executed. This user-space version of
gatord has most, but not all of the functionality of the
standard version of
gatord running with the
For more information, see README.md
After making sure that you have root privileges, enter the following to
execute the gator daemon:
gatord uses port 8080 for communication with the host, but you
can adjust this by launching
gatord with the port number as
a parameter. For example:
./gatord -p 5050 &
Additionally, specify the port number using the Capture & Analysis
Options dialog box by appending a colon followed by the port
number to the IP address in the address field. For example, if the address
is 10.99.28.54 and the port is 5050 you enter 10.99.28.54:5050. If you do
not provide a port number, the default port is used.
If you use Security-Enhanced Linux (SELinux), you might see one of the following errors
Unable to mount the gator filesystem needed for profiling.
Unable to load (insmod) gator.ko driver:
>>> gator.ko must be built against the current kernel version & configuration
>>> See dmesg for more details
If you see one of these error messages, enter the
dmesg command for more details.
dmesg contains the text
initialized (dev gatorfs, type gatorfs), not configured for
labeling, enter the following command to disable SELinux:
started, you can re-enable SELinux by using the following