> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/partek/partek-genomics-suite/installation-guide/floating-locked-floating-installation/license-server-faqs.md).

# License Server FAQ's

Frequently Asked Questions related to Partek Genomics Suite License Server

## What is required to access the log file to find out who is using the software?

The log file is written on the computer that runs the license server. The user specifies the location of this log file when running the lmgrd command.

## Where is the log file and how do I access it?

The log file can be found in the following folders, depending on your license server's platform:

* Windows: "C:\FLEXnet" or "C:\Program Files (x86)\FlexNet Publisher License Server Manager\logs\parteklm"
* Linux: “/opt/FlexNet”
* Mac: "/Users/Shared/FlexNet"

To access the log file, open the file on the license server with your favorite text editor.

## Can more than one person access the log file?

The log file may be viewable by more than one person but only on the same computer as the license server.

## When the number of licensed users is already reached, is there a way to "force someone off"?

Restarting the license server will temporarily force users off of the server.

An option file may be used to prevent certain users/computer network addresses from using license features (see: the Managing the Options File chapter of the [FlexNet License Administration Guide](http://packages.partek.com/bin/flexnet/FLEXnet-License_Administration_Guide.pdf)) by using the EXCLUDE or EXCLUDEALL keywords. If you set up an options file with EXCLUDE or EXCLUDEALL and restart the license server, you will "kick out a user" but not other users.


---

# 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://help.bioinsight.illumina.com/partek/partek-genomics-suite/installation-guide/floating-locked-floating-installation/license-server-faqs.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.