RUP(1)

πŸ“¦
version 4.0.1 Β· 3 versions
, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

πŸ’« RUP(1) β€” the remote uptime display situation πŸ’«

okay bestie, welcome to the rup page from the Linux Programmer's Manuel. yes it's a man page, yes it's about remote uptime, and yes we're gonna make it cute. let's go πŸ¦‹


✨ NAME ✨

rup β€” remote uptime display πŸ•βœ¨


🌸 SYNOPSIS 🌸

rup { -u | -v | hosts ... }

πŸ’– DESCRIPTION πŸ’–

so like, rup shows you a lil summary of the current status of a particular host, or literally every host on the local network. it's giving "who's awake and how long have they been awake" πŸ’…

the output tells you:

  • how long the system has been up ⏰
  • the number of users currently on the system β€” but ONLY if the system is running the current version of rpc.rstatd(8) πŸ™ˆ
  • the load averages πŸ“ˆ

and the load average numbers? they give you the number of jobs in the run queue, averaged over 1, 5 and 15 minutes. iconic trio behavior tbh.

⚠️ real talk though: the rpc.rstatd(8) daemon must be running on the remote host or this command simply will not work. no daemon, no vibes, no output. 😭

also, rup uses an RPC protocol defined in /usr/include/rpcsvc/rstat.x β€” yes that's the actual path, keep it πŸ’–


πŸŽ€ COMMAND LINE OPTIONS πŸŽ€

  • -v β€” prints the current version of rup and exits. short and sweet, main character energy ✨
  • -u β€” broadcasts for infornmation from machines capable of returning users information implemented in the newest version of rpc.rstatd. (that's "infornmation" with the typo, we don't fix the classics, we respect the lore 🫢)

πŸ’… DIAGNOSTICS πŸ’…

these are the lil drama moments rup can hand you. read them, know them, love them.

  • rup: RPC: Program not registered the rpc.rstatd(8) daemon has not been started on the remote host. bestie is not home πŸšͺπŸ’€
  • rup: RPC: Timed out a communication error occurred. either the network is excessively congested, or the rpc.rstatd(8) daemon has terminated on the remote host. it's giving chaos either way 😭
  • rup: RPC: Port mapper failure - RPC: Timed out the remote host is not running the portmapper (see rpc.rstatd(8)) and cannot accomodate any RPC-based services. the host may be down. πŸ’€ (again, "accomodate" β€” original spelling, we preserve it, periodt)

🌈 SEE ALSO 🌈


πŸ‘‘ HISTORY πŸ‘‘

the rup command appeared in SunOS. ancient. legendary. still here. ⭐


πŸ’€ BUGS πŸ’€

the sorting options are not implemented. that's it, that's the bug. no sorting for you bestie, sorry πŸ™ˆ


🫢 AUTHOR 🫢

Adam Migus (amigus@cs.mun.ca) β€” thank you for your service πŸŽ€


okay that's the whole page!! and for the cute sign-off: this lil beauty comes from Linux 1.2, dated Sept 25, 1995 β€” old enough to be a vintage collectible, still out here explaining RPC to us. slay forever πŸ’–βœ¨πŸŒΈπŸ¦‹πŸ’…

πŸ“¦ where this page comes from