> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.5/archive/legacy-license-server-floating-licenses/installing-on-linux.md).

# Installing on Linux

## **Linux installation procedure**

The Linux installer is a self-unpacking binary. You may need to set file permissions to executable before running it:

```
chmod +x ./lmadmin-x64_lsb-11_16_0_0.bin
```

lmadmin or lmgrd require LSB support installed:

```
[Redhat/Fedora]
yum install redhat-lsb-core
[Ubuntu]
apt-get install lsb-core
[Debian]
ln -s /usr/lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3
```

**If you decided to use 'lmgrd' instead of 'lmadmin'**, in addition you will have to:

```
sudo mkdir /usr/tmp
sudo chmod 777 /usr/tmp
```

## **Starting as a service**

The Linux installer does not configure the server to start automatically. If your distribution uses SysV style init, check the \[install\_dir]/examples/service/lmadmin script. For a systemd service script example, check \[install\_dir]/examples/systemd/

If you used 'lmgrd' instead of 'lmadmin' (and thus don't have the examples/ directory), you can find an example SysV-style script [here](https://github.com/HexRaysSA/ida-docs/blob/9.4/archive/legacy-license-server-floating-licenses/assets/example_lmadmin_as_a_service.txt) and systemd-style script [here](https://github.com/HexRaysSA/ida-docs/blob/9.4/archive/legacy-license-server-floating-licenses/assets/lmgrd.service.txt).

## **Misc.**

See also "Installing lmadmin License Server Manager as an Operating System Service" in the License Administration Guide.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/ida-9.5/archive/legacy-license-server-floating-licenses/installing-on-linux.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.