# Installing on OS X

## **Starting as a service**

The OS X lmadmin installer does not configure the server to start automatically.

Check the \[install\_dir]/examples/service/ directory for a sample startup script or \[install\_dir]/examples/launchd/ for a launchd example plist.

For the sample plist file to work, the UserName and GroupName key values need to be changed from "nobody" to a production UserName and GroupName.

If you use 'lmgrd' instead of 'lmadmin' (and thus don't have the examples/ directory), you can find an example script or a launchd plist below.

<table data-header-hidden><thead><tr><th></th><th data-type="files"></th></tr></thead><tbody><tr><td><strong>exemplary script</strong></td><td><a href="/files/5aVF1Z6Amjma4dyWmOQk">/files/5aVF1Z6Amjma4dyWmOQk</a></td></tr><tr><td>l<strong>aunchd plist</strong></td><td><a href="/files/e4PNCueMa5avdHrieOuv">/files/e4PNCueMa5avdHrieOuv</a></td></tr><tr><td></td><td></td></tr></tbody></table>

For macOS earlier than 10.13, plist files should be placed in /System/Library/LaunchDaemons rather than in /System/Library/LaunchAgents. The naming convention for plist files is com.apple.filename.plist.

For macOS 10.13 or later, either location works, and there are no restrictions for plist file naming.

## **Misc.**

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


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hex-rays.com/8.4/admin-guide/legacy-license-server-floating-licenses/installing-on-os-x.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.