Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #725
Difficulty: Medium
Barbara Liskov developed the Liskov substitution principle, which guarantees semantic interoperability of data types in a hierarchy.
True or False?
Linux & Unix Commands - Search Man Pages

rup(1) [redhat man page]

RUP(1)							    BSD General Commands Manual 						    RUP(1)

rup -- remote status display SYNOPSIS
rup [-dshlt] [host ...] DESCRIPTION
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 aver- aged 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 syncronization on a network. -s Print time data in seconds (seconds of uptime or seconds since the epoch), for scripts. -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 command to work. rup uses an RPC protocol defined in /usr/include/rpcsvc/rstat.x. EXAMPLE
example% rup otherhost otherhost up 6 days, 16:45, load average: 0.20, 0.23, 0.18 example% DIAGNOSTICS
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 excessively 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 accomodate any RPC-based services. The host may be down. SEE ALSO
ruptime(1), portmap(8), rpc.rstatd(8) HISTORY
The rup command appeared in SunOS. Linux NetKit (0.17) August 15, 1999 Linux NetKit (0.17)

Check Out this Related Man Page

ruptime(1)						      General Commands Manual							ruptime(1)

ruptime - show status of local machines SYNOPSIS
outputs a status line for each machine on the local network that is running the daemon. status lines are formed from packets broadcast once every 3 minutes between daemons (see rwhod(1M)) on each host on the network. Each status line has a field for the name of the machine, the status of the machine (up or down), how long the machine has been up or down, the number of users logged into the machine, and the 1-, 5- and 15-minute load averages for the machine when the packet was sent. The status of the machine is reported as ``up'' unless no report has been received from the machine for 11 minutes or more. The length of time that the machine has been up is shown as: Load averages are the average number of jobs in the run queue over the last 1-, 5- and 15-minute intervals when the packet was sent. An example status line output by might be: The above status line would be interpreted as follows: is presently ``up'' and has been up for 1 day, 5 hours and 15 minutes. It currently has 7 users logged in. Over the last 1-minute inter- val, an average of 1.47 jobs were in the run queue. Over the last 5-minute interval, an average of 1.16 jobs were in the run queue. Over the last 15-minute interval, an average of 0.80 jobs were in the run queue. If a user has not used the system for an hour or more, the user is considered idle. Idle users are not shown unless the option is speci- fied. Options If no options are specified, the listing is sorted by host name. Options change sorting order as follows: Sort by load average. Sort by up time. Sort by the number of users. Reverse the sort order. DIAGNOSTICS
No status report files in Ask the system administrator to check whether the daemon is running. AUTHOR
was developed by the University of California, Berkeley. FILES
Data files SEE ALSO
rwho(1), rwhod(1M). ruptime(1)

Featured Tech Videos