icon Top 9 categories map      RocketAware >


Tips: Browse or Search all pages for efficient awareness of more than 6000 of the most popular reusable and open source applications, functions, libraries, and FAQs.

The "RKT couplings" below include links to source code, updates, additional information, advice, FAQs, and overviews.


Search all pages


By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Integer, Floating point, Matrix, Statistics, Boolean, ...

Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...


RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD RedHat Solaris Others

RUP(1)                     OpenBSD Reference Manual                     RUP(1)

     rup - remote status display

     rup [-dhlt] [host ...]

     rup displays a summary of the current system status of a particular host
     or all hosts on the local network.  The output shows the current time of
     day, how long the system has been up, and the load averages.  The load
     average numbers give the number of jobs in the run queue averaged over 1,
     5 and 15 minutes.

     The following options are available:

     -d      For each host, report what its local time is.  This is useful for
             checking time synchronization on a network.

     -h      Sort the display alphabetically by host name.

     -l      Sort the display by load average.

     -t      Sort the display by up time.

     The rpc.rstatd(8) daemon must be running on the remote host for this com-
     mand to work.  rup uses an RPC protocol defined in /usr/in-

           example% rup otherhost
           otherhost      up 6 days, 16:45,  load average: 0.20, 0.23, 0.18

     rup: RPC: Program not registered
             The rpc.rstatd(8) daemon has not been started on the remote host.

     rup: RPC: Timed out
             A communication error occurred.  Either the network is excessive-
             ly congested, or the rpc.rstatd(8) daemon has terminated on the
             remote host.

     rup: RPC: Port mapper failure - RPC: Timed out
             The remote host is not running the portmapper (see portmap(8)),
             and cannot accommodate any RPC-based services.  The host may be

     ruptime(1),  portmap(8),  rpc.rstatd(8)

     The rup command appeared in SunOS.

OpenBSD 2.6                      June 7, 1993                                1

Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.

(Corrections, notes, and links courtesy of RocketAware.com)

[Detailed Topics]
FreeBSD Sources for rup(1)
OpenBSD sources for rup(1)

[Overview Topics]

Up to: Remote Process Creation and Control - Methods of starting and controlling processes remotely. (telnet, login, rexec, et al.)

RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD RedHat Solaris Others

Rapid-Links: Search | About | Comments | Submit Path: RocketAware > rup.1/
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments