> For the complete documentation index, see [llms.txt](https://usdrcg.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usdrcg.gitbook.io/docs/practice/about-legacy/logging-in-to-an-interactive-session-qlogin.md).

# Logging in to an interactive session - qlogin

To start an interactive session on a compute node use the`qlogin` command. This is useful for menu-driven applications or other interactive programs.

By default qlogin will request 1GB of memory, 1 CPU core, and 1GB of scratch disk.

The qlogin command can also request a specific number of CPU cores, RAM, or scratch disk space (non-shared, local disk available available in /scratch on each compute node) for your interactive session. For example, the following command requests 4 CPU cores, 24GB of RAM, and 10GB of scratch disk:

`qlogin -pe threaded 4 -l scratch_free=10G,mem_free=24G`

If you only wish to request 24GB of ram, use:`qlogin -l mem_free=24G`

To exit your interactive session type`logout`.


---

# 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 dynamically by asking a question.

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

```
GET https://usdrcg.gitbook.io/docs/practice/about-legacy/logging-in-to-an-interactive-session-qlogin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.