RUSHWHO(1)
π RUSHWHO(1) π
okay bestie, welcome to the Rush User Reference β this is rushwho, and she's here to show you who is logged on by rush(1). yes, that's the whole vibe. let's get into it π«Ά
πΈ NAME πΈ
rushwho β show who is logged on by rush(1)
β¨ SYNOPSIS β¨
rushwho [-Hh] [-F STRING] [-f DIR] [--file=DIR] [--format=STRING]
[--help] [--no-header] [--usage] [--version]
π NOTE π
okay so real talk, this manpage is a short description of rushwho. if you want the full deep-dive β examples, usage recommendations, the whole main-character arc β you gotta go read the manual GNU Rush -- a restricted user shell, and she lives in texinfo format. if the info reader and the rush documentation are properly installed on your system, this command:
info rushwho
should hand you the complete manual. slay.
you can also peep the manual using info mode in emacs(1), or find it in various formats online at:
http://www.gnu.org.ua/software/rush/manual
π important: if any discrepancies occur between this manpage and the Manual, the later shall be considered the authoritative source. so like, the Manual wins, no cap.
π¦ DESCRIPTION π¦
Displays a list of users who are currently logged in by rush(1). The utility operates on the default accounting database, which is maintained if rush(1) runs in accounting mode. that's the tea β
π OPTIONS π
-F,--format=STRINGβ Use STRING instead of the default format. See the section FORMAT for a detailed discussion of the format syntax. If the STRING begins with a@, then this character is removed from it, and the resulting string is regarded as a name of the file to read. The file is read literally, except that lines beginning with a semicolon are ignored.-f,--file=DIRβ Look for database files in DIR.-n,--count=NUMBERβ Show at most NUMBER records.
π Other options π
-h,--helpβ Give this help list.--usageβ Give a short usage message.--versionβ Print program version.
π ENVIRONMENT π
RUSHWHO_FORMATβ When set, supplies a format string to use instead of the built-in format. If the value begins with a@sign, rest of characters is treated as the name of file to read the format from, similarly to the--formatoption, which see.
The precedence rule for format selection is:
- The
--formatoption. - The
RUSHWHO_FORMATenvironment variable. - Built-in format.
so yeah, option > env var > built-in. that's the hierarchy, periodt π
π FORMAT π
The format string supplied with the -F (--format) option controls the output of every record from the GNU Rush accounting database. It consists of the following classes of objects:
Ordinary characters
These are copied to the output verbatim. literally just vibes, straight through.
Escapes
An escape is a backslash, followed by a single character. It is interpreted according to the following table:
\aβ Audible bell character (ASCII 7)\bβ Backspace character (ASCII 8)\eβ Escape character (ASCII 27)\fβ Form-feed character (ASCII 12)\nβ Newline character (ASCII 10)\rβ Carriage return character (ASCII 13)\tβ Horizontal tabulation character (ASCII 9)\vβ Vertical tabulation character (ASCII 11)\\β A single backslash\"β A double-quote.
Any escape not listed in the table above results in its second character being output. so like, not on the list? you get the second char, no questions asked π
Quoted strings
Strings are delimited by single or double quotes. Within a string escape sequences are interpreted as described above.
Format specifications
Format specification can be regarded as a kind of function, which outputs a particular piece of information from the database record. Syntactically, format specification starts with an opening brace and ends with a closing brace. The first word after the brace is the name of the specification. The rest of words are positional arguments followed by keyword arguments. Both are optional. A keyword argument begins with a colon.
The available format specifications are:
(newline [COUNT])β Causes the newline character to be output. If the optional count is supplied, that many newlines will be printed(tab [COUNT])β Advance to the next tab stop in the output stream. If optional COUNT is present, then skip that many tab stops. Each tab stop is eight characters long.
The following specifications output particular fields of a database record. They all take two positional arguments: WIDTH and TITLE.
The first argument, WIDTH sets the maximum output length for this specification. If the number of characters actually output is less than the width, they will be padded with whitespace either to the left or to the right, depending on the presence of the :right keyword argument. If the number of characters is greater than WIDTH, they will be truncated to fit. If WIDTH is not given, the exact data are output as is.
The second argument, TITLE, gives the title of this column for the heading line. By default no title is output.
Every field specification accepts at least two keyword arguments. The keyword :right may be used to request alignment to the right for the data. This keyword is ignored if WIDTH is not given.
The keyword :empty followed by a string causes the program to output that string if the resulting value for this specification would otherwise be empty.
(user WIDTH TITLE [:empty REPL][:right])β Print the user login name.(time WIDTH TITLE [:empty REPL][:right][:format DATE-FORMAT])β Date and time when the session started. The word start-time can be used instead of time.
The :format keyword introduces the strftime(3) format string to be used when converting the date for printing. The default value is "%a %H:%M".
(duration WIDTH TITLE [:empty REPL][:right])β Total time of the session duration.(rule WIDTH TITLE [:right])β The tag of the rule that was used to serve the user.(command WIDTH TITLE [:empty REPL][:right])β Command line being executed.(pid WIDTH TITLE [:right])β PID of the process.
For example, the following is the default format for rushwho. It is written in a form, suitable for use in a file supplied with the --format=@FILE option:
(user 10 Login)" "
(rule 8 Rule)" "
(start-time 0 Start)" "
(duration 9 Time)" "
(pid 10 PID)" "
(command 28 Command)
π SEE ALSO π
π§ AUTHORS π§
Sergey Poznyakoff
π BUG REPORTS π
Report bugs to <bug-rush@gnu.org.ua>.
β COPYRIGHT β
Copyright Β© 2016 Sergey Poznyakoff
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
π bestie the "NO WARRANTY" is in caps for a reason β do not come for her if it breaks, she told you upfront fr fr.
and that's a wrap, my love π this was rushwho, part of the Rush User Reference, dated August 17, 2016. go forth and see who's logged on π¦β¨
π¦ where this page comes from
- debian trixie: rush 2.4-1 Β· GPL-3.0-or-later
- epel 10: rush 2.4-1.el10_0 Β· GPL-3.0-or-later AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LGPL-3.0-or-later AND GFDL-1.1-or-later AND GFDL-1.3-or-later
- epel 9: rush 2.4-1.el9 Β· GPL-3.0-or-later AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LGPL-3.0-or-later AND GFDL-1.1-or-later AND GFDL-1.3-or-later
- fedora 43: rush 2.4-3.fc43 Β· GPL-3.0-or-later AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LGPL-3.0-or-later AND GFDL-1.1-or-later AND GFDL-1.3-or-later
- fedora 44: rush 2.4-4.fc44 Β· GPL-3.0-or-later AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LGPL-3.0-or-later AND GFDL-1.1-or-later AND GFDL-1.3-or-later
- nixos 26.05: rush 2.4
- nixpkgs unstable: rush 2.4
- ubuntu questing: rush 2.4-1
- ubuntu resolute: rush 2.4-1build1 Β· GPL-3.0-or-later
- ubuntu stonking: rush 2.4-1build1 Β· GPL-3.0-or-later
- Copyright (C) 2016-2024 Sergey Poznyakoff
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms