lnst-slave man page

lnst-slave — Linux Network Stack Test slave daemon


lnst-slave [-d] [-e] [-h] [-i pidfile] [-p port_number]


Linux Network Stack Test is a tool that supports development and execution of automated and portable network tests. For detailed description of the architecture of LNST please refer to project website (link listed on Internet Resources bellow).

lnst-slave is a daemon script that runs in the background and waits for incomming commands from a controller.


-d, --debug

Toggle emitting debugging messages.

-e, --daemonize

Detach from parent process and run in background.

-h, --help

Display usage of this command.

-i, --pidfile=file

File to write damonized process' PID to.

-m, --no-colours

Disable coloured terminal output.

-p, --port=port_number

The port number lnst-slave should listen on for incomming commands.


lnst-slave will look for configuration in the following location:


For further description of file format or configuration options available, please refer to the configuration file itself, where each option is documented.


Apart from configuration, there are few important locations that lnst-slave works with. All bellow mentioned paths can be changed in the configuration file.

Log Path

Every test exectution and all the commands run by lnst-slave during the test are logged to the following location:


Cache Location

Test modules and tools used by the controllers with this slave are cached in resources cache. The cache is by default located at:


The cache is fully under control of the lnst-slave daemon and is managed automatically. Making any modifications by hand is not recommended.

Internet Resources

Project Homepage:      http://lnst-project.org/
Online Documentation:  https://github.com/jpirko/lnst/wiki#learn
Git Source Tree:       https://github.com/jpirko/lnst
Mailing List:          <lnst-developers@lists.fedorahosted.org>


Jiri Pirko <jiri@resnulli.us>
Jan Tluka <jtluka@redhat.com>
Ondrej Lichtner <olichtne@redhat.com>
Jiri Prochazka <jprochaz@redhat.com>
Jiri Zupka <jzupka@redhat.com>
Radek Pazdera <radek@pazdera.co.uk>