RUSHLAST(1)

πŸ“¦
version 2.4 Β· 3 versions
, in debian trixie, epel 10, epel 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ NAME ✨

rushlast β€” show listing of last Rush logins πŸ’…

okay so bestie, this is a page from the Rush User Reference, manual section 1 (that's "user commands" energy, general-purpose stuff you just run). Say hi to rushlast πŸ‘‹


πŸ“œ SYNOPSIS πŸ“œ

rushlast [-Hh] [-F STRING] [-f DIR] [-n NUMBER] [--file=DIR]
[--format=STRING] [--forward] [--help] [--no-header] [--number=NUMBER]
[--usage] [--version] [USER...]

🫢 NOTE 🫢

ngl this manpage is just the short description of rushlast. For the whole detailed discussion β€” examples, usage recommendations, all of it β€” go read the manual GNU Rush -- a restricted user shell, which lives in texinfo format. If the info reader and the rush documentation are properly installed on your system, this command

info rushlast

should give you access to the complete manual. slay πŸŽ€

You can also view the manual using the info mode in emacs(1), or find it in various formats online at

http://www.gnu.org.ua/software/rush/manual
⚠️ If any discrepancies occur between this manpage and the Manual, the later shall be considered the authoritative source. So like, the Manual is the main character here, this page is the bestie who's just giving you the recap. πŸ’€

πŸ’« DESCRIPTION πŸ’«

It searches back through the GNU Rush database and shows you a list of all user sessions since the database was created. It's giving receipts. πŸ•΅οΈβ€β™€οΈ

The utility operates on the default accounting database, which is maintained only if rush(1) runs in accounting mode. No accounting mode, no database, no tea. πŸ“


πŸ‘‘ OPTIONS πŸ‘‘

  • -F, --format=STRING β€” Use STRING instead of the default format. Use STRING instead of the default format. (yes bestie, it says it twice, the manpage is just that committed πŸ’…) See the section FORMATS, 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.
  • --forward β€” Show entries in chronological order.
  • -H, --no-header β€” Do not display header line.
  • -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 🌈

  • RUSHLAST_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 --format option, which see.

The precedence rule for format selection is:

  1. The --format option.
  2. The RUSHLAST_FORMAT environment variable.
  3. Built-in format.

So like, option beats env var beats the built-in default. That's the hierarchy, no cap. πŸ“Š


🌸 FORMATS 🌸

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. Zero drama, they just show up as themselves. ✨

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 it just shrugs and gives you the character after the backslash, iconic 🫠)

Quoted strings

Strings are delimited by single or double quotes. Within a string escape sequences are interpreted as described above.

Format specifications

A 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.
  • (start-time WIDTH TITLE [:empty REPL][:right][:format DATE-FORMAT]) β€” Date and time when the session started.

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".

  • (stop-time WIDTH TITLE [:empty REPL][:right][:format DATE-FORMAT]) β€” Time when the command finished. If it is still running, the word running is output.
  • (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.

The default format is:

(user 10 Login)" "
(rule 8 Rule)" "
(start-time 0 Start)" "
(stop-time 0 Stop)" "
(duration 7 Time)" "
(command 32 Command)

πŸ”— SEE ALSO πŸ”—

rush(1), rushwho(1).


πŸŽ€ AUTHORS πŸŽ€

Sergey Poznyakoff


😭 BUG REPORTS 😭

Report bugs to <bug-rush@gnu.org.ua>.


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.


and that's the whole thing bestie, we ate and left no crumbs πŸ’…βœ¨ this was RUSHLAST, section 1 of the Rush User Reference, dated August 17, 2016 β€” periodt, go read the real manual for the full lore πŸ¦‹πŸŽ€

πŸ“¦ where this page comes from