|
|
|
rtsched(1) -- execute process with real-time priority
|
|
Rtsched executes command with POSIX or HP-UX real-time priority, or changes the real-time priority of currently executing process pid. All POSIX real-time priority processes are of greater scheduling importance than processes with HP-UX real-time or HP-UX timeshare priority. All HP-UX real-time priority processes are of greater scheduling importance than HP-UX timeshare priority processes, but are... |
|
runacct(1m) -- run daily accounting
|
|
runacct is the main daily accounting shell procedure. It is normally initiated via cron(1M). runacct processes connect, fee, disk, and process accounting files. It also prepares summary files for prdaily or billing purposes. runacct takes care not to damage active accounting files or summary files in the event of errors. It records its progress by writing descriptive diagnostic messages into activ... |
|
|
rup(1) -- show host status of local machines (RPC version)
|
|
rup gives a status similar to uptime for remote machines. It broadcasts on the local network and displays the responses it receives. Though the listing is normally in the order responses are received, the order can be changed by using command-line options. The broadcast process takes about two minutes. When host arguments are given, instead of broadcasting, rup only queries the list of specified h... |
|
ruptime(1) -- show status of local machines
|
|
ruptime outputs a status line for each machine on the local network that is running the rwho daemon. ruptime's status lines are formed from packets broadcast once every 3 minutes between rwho 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 ... |
|
rusers(1) -- determine who is logged in on machines on local network
|
|
rusers produces output similar to the "quick" option of who(1), but for remote machines. It broadcasts on the local network and prints the responses it receives. Though the listing is normally in the order that responses are received, the order can be changed by specifying a command-line option. The broadcast process takes about two minutes. When host arguments are given, instead of broadcasting... |
|
rusersd(1m) -- network username server
|
|
rusersd is an RPC server that returns a list of users on the network. The rusers command prints this information (see rusers(1)). inetd invokes rusersd through /etc/inetd.conf (see inetd(1M)). |
|
rvxdump(1m) -- incremental VxFS file system dump, local or across network
|
|
vxdump copies to magnetic tape all files in the vxfs filesystem that have been changed after a certain date. This information is derived from the files /etc/fstab and a timestamp file, by default /etc/dumpdates. rvxdump copies the files to a tape drive on a remote system. rvxdump runs a process, /usr/sbin/rmt, on the remote machine to access the tape device. vxdump and rvxdump support both getopt(... |
|
rvxrestore(1m) -- restore file system incrementally, local or across network
|
|
vxrestore and rvxrestore read tapes previously dumped by the vxdump or rvxdump command (see vxdump(1M)). vxrestore restores from tape on the local system; rvxrestore restores from tape on a remote system. rvxrestore runs /usr/sbin/rmt on the remote machine to access the tape device. vxrestore and rvxrestore support both getopt(3C) and traditional restore command line invocations as shown above. Th... |
|
rwall(1m) -- write to all users over a network
|
|
rwall reads a message from standard input until EOF, then sends the message, preceded by the line Broadcast Message ..., to all users logged in on the specified host machines. With the -n option, rwall sends the message to the specified network hosts defined in /etc/netgroup (see netgroup(4)). A machine can only receive such a message if it is running rwalld, which is normally started from /etc/in... |
|
rwalld(1m) -- network rwall server
|
|
rwalld is an RPC server that handles rwall requests (see rwall(1)). rwalld calls wall to send a message to all users logged into the host on which rwalld is running (see wall(1)). inetd invokes rwalld through /etc/inetd.conf (see inetd(1M)). |
|
rwho(1) -- show who is logged in on local machines
|
|
rwho produces output similar to the output of the HP-UX who command for all machines on the local network that are running the rwho daemon (see who(1) and rwhod(1M)). If rwhod has not received a report from a machine for 11 minutes, rwho assumes the machine is down and rwho does not report users last known to be logged into that machine. rwho's output line has fields for the name of the user, the... |
|
rwhod(1m) -- system status server
|
|
rwhod is the server that maintains the database used by rwho and ruptime (see rwho(1) and ruptime(1)). rwhod sends status information to and receives status information from other nodes on the local network that are running rwhod. rwhod is started at system boot time if the RWHOD variable is set to 1 in the file /etc/rc.config.d/netdaemons. As an information sender, it periodically queries the sta... |
|
sa1(1m) -- system activity report package
|
|
System activity data can be accessed at the special request of a user (see sar(1M)) and automatically on a routine basis as described here. The operating system contains a number of counters that are incremented as various system actions occur. These include CPU utilization counters, buffer usage counters, disk and tape I/O activity counters, tty device activity counters, switching and system-call... |
|
sa2(1m) -- system activity report package
|
|
System activity data can be accessed at the special request of a user (see sar(1M)) and automatically on a routine basis as described here. The operating system contains a number of counters that are incremented as various system actions occur. These include CPU utilization counters, buffer usage counters, disk and tape I/O activity counters, tty device activity counters, switching and system-call... |
|
sact(1) -- print current SCCS file editing activity
|
|
The sact command informs the user of any impending deltas to a named SCCS file. This situation occurs when get -e has been previously executed without a subsequent execution of delta (see delta(1) and get(1)). If a directory is named on the command line, sact behaves as though each file in the directory were specified as a named file, except that non-SCCS files (last component of path name does no... |
