> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/man/man1/ruptime.1.md).

# ruptime.1

`ruptime` — 显示本地机器的主机状态

## 名称

`ruptime`

## 概要

`ruptime [-alrtu] [host ...]`

## 描述

`ruptime` 实用程序为本地网络上的每台机器给出类似 [uptime(1)](https://github.com/FreeBSD-Ask/freebsd-man-sc/blob/main/man1/uptime.1.md) 的状态行；这些状态行由网络上每台主机每三分钟广播一次的数据包形成。

如果未给出操作数，`ruptime` 显示所有机器的正常运行时间状态；否则仅显示命令行上指定的主机。如果在命令行上指定了主机，排序顺序等同于在命令行上指定主机的顺序。

11 分钟内未收到状态报告的机器显示为停机，4 天内未收到状态报告的机器根本不会显示在列表中。

选项如下：

**`-a`** 包含所有用户。默认情况下，如果用户一小时或更长时间未向系统输入，则该用户将从输出中省略。

**`-l`** 按负载平均值排序。

**`-r`** 反转排序顺序。

**`-t`** 按正常运行时间排序。

**`-u`** 按用户数排序。

默认列表按主机名排序。

## 文件

**/var/rwho/whod.\*** 数据文件

## 参见

[rwho(1)](/man/man1/rwho.1.md), [uptime(1)](https://github.com/FreeBSD-Ask/freebsd-man-sc/blob/main/man1/uptime.1.md), rwhod(8)

## 历史

`ruptime` 实用程序出现于 4.2BSD。


---

# 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://book.bsdcn.org/man/man1/ruptime.1.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.