Files
threshold/website/content/docs/commands/cache/status.mdx
T

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

52 lines
1.1 KiB
Plaintext
Raw Normal View History

---
layout: docs
2024-05-22 11:11:48 -07:00
page_title: cache status - Command
description: |-
2024-05-22 11:11:48 -07:00
The "cache status" command lets you manually check the status of the Boundary cache.
---
2024-05-22 11:11:48 -07:00
# cache status
2024-05-22 11:11:48 -07:00
Command: `boundary cache status`
2024-05-22 11:11:48 -07:00
The `boundary cache status` command lets you manually check the status of the Boundary cache.
Boundary prints out a status report that includes configuration, user, and resource information.
## Example
2024-05-22 11:11:48 -07:00
The following command checks the status of the Boundary cache:
```shell-session
2024-05-22 11:11:48 -07:00
$ boundary cache status
```
**Example output:**
<CodeBlockConfig hideClipboard>
```plaintext
Status:
Domain Socket: /home/my_user/.boundary/socket/daemon.sock
Log Location: /home/my_user/.boundary/cache.log
Uptime: 15m22s
User Count: 1
```
</CodeBlockConfig>
## Usage
<CodeBlockConfig hideClipboard>
```shell-session
2024-05-22 11:11:48 -07:00
$ boundary cache status [options] [args]
```
</CodeBlockConfig>
### Command options
- `output-curl-string` - Specifies that Boundary should print an equivalent cURL command string and exit, instead of executing the request.
The default value is `false`.
2024-05-22 11:11:48 -07:00
@include 'cmd-option-note.mdx'