Run modes

• ./LoadTeam – normal app window (interactive)
• ./LoadTeam --mode console – live progress in the terminal
• ./LoadTeam --mode headless – hidden background process
• ./LoadTeam --mode service – systemd service (needs root to install)

1. Extract and configure

The tarball contains the LoadTeam binary and everything it needs. You can ignore install.sh and run the binary directly:

tar xzf LoadTeamLinux.tar.gz
cd loadteam
chmod +x LoadTeam

The non-interactive modes can't prompt for your secret key, so set it first in LoadTeam.ini next to the binary (copy LoadTeam.sample.ini):

apikey=YOUR_SECRET_KEY

Alternatively pass --api-key YOUR_SECRET_KEY on the command line.

Optional – how hard LoadTeam works the CPU while you are using the computer and while it is idle, from 0.0 to 1.0 (defaults shown):

activeintensity=0.2
idleintensity=0.8

Or pass --active-intensity 0.2 --idle-intensity 0.8 on the command line; command line options override LoadTeam.ini.

2. Run as a systemd service

Registers a system service that starts at boot and runs regardless of who is logged in. This needs root, so run it with sudo:

sudo ./LoadTeam --mode service --install
sudo systemctl enable --now loadteam

To stop and remove the service later:

sudo ./LoadTeam --mode service --uninstall

The unit is named loadteam. Check it with systemctl status loadteam and follow logs with journalctl -u loadteam -f.

3. Headless or console mode

Run LoadTeam under your own account instead of as a service – hidden (headless) or with live progress in the terminal (console):

./LoadTeam --mode headless
./LoadTeam --mode console

For an unattended box, run headless inside tmux/screen, or wire up your own per-user systemd unit (systemctl --user).

Notes

• 64-bit Linux (x86-64)
• Self-contained – no .NET runtime to install
• Service mode is the only mode that needs root
• Keep all files in the folder together when you move it

Need your secret key? It's on your account page.