- 浏览: 424357 次
最新评论
-
u010297957:
我觉得不严谨,可以看我这篇:http://blog.csdn. ...
java内存分配机制 -
yuvyuvyuv:
Oracle中有exists关键字...
在我眼中的Oracle世界 -
903293718:
Oracle中没有exists()函数?
在我眼中的Oracle世界 -
hngmduyi:
...
在我眼中的Oracle世界 -
308202251:
非常不错
最近的读书计划
UnixWare7 实时系统性能监视工具 rtpm 使用指南
rtpm
rtpm -- <!--Meta NM "rtpm"-->real time performance monitor <!--Meta DN "real time performance monitor"-->
Synopsis
rtpm [-h history_buffer_size] [interval]Description
The command rtpm displays operating system performance metrics and usage information in an interactive real-time curses-based graphical display.The interval argument specifies the time in seconds between successive samples of the performance information. The default interval is two seconds.
The history_buffer_size argument specifies the number of history data points rtpm saves for plotting metrics. The default value for the history buffer size is the number of columns on the screen, as specified by the $COLUMNS environment variable.
Screen size
Using the IOCGWINSZ ioctl system call, rtpm attempts to automatically determine your screen size and adjust the display accordingly. However, if the $LINES and $COLUMNS environment variables are set, they take precedence over the ioctl call. In no case will the screen size be smaller than 24 rows by 80 columns.Screen layout
The rtpm screen is divided into three areas. The top portion of the screen shows the graphical display, the bottom line of the screen displays the status of the monitor, and 14 lines between the graphical display area and the status line display text-based metric information.The graphical display area contains a bar graph of CPU consumption, plots of metric data, or both. The text-based metric display area consists of numeric metric data, labels for the metric data, and subscreen headers. The numeric metric data, subscreen headers, and plot titles are cursor addressable.
Views
The metrics are available in either of two views: a CPU view and a CG view. In the CPU view, the metrics are displayed on a per-processor basis. In the CG view, the metrics are displayed on a per-CPU group basis, where each CPU group consists of a set of processors.You can toggle between views using the <g> or <G> key. The default view is the CPU view.
Status line
The bottom line of the screen is the status display area. Typically, it contains the name of the machine, as returned by the uname(2) system call, the current date and time, the requested sampling interval, and the actual interval sampled. Two other messages may be displayed on the status line. The first is the messageLOCKED
that means rtpm has been locked in memory by the plock(2) system call; only privileged users are allowed to do this. The second message is Enter <?> for help
. Cursor motions
Move the cursor by pressing any of the following case-insensitive keys:- the terminal arrow keys
- <H>, <J>, <K>, <L> (as in vi)
- <Ctrl><F>, <Ctrl><B>, <Ctrl><P>, <Ctrl><N> (as in emacs)
Plotting metrics
When the cursor is on a numeric metric data item, pressing either <Space> or the <Return> key causes the metric to be plotted in the graphical display area. The number of concurrent plots allowed depends on the size of the screen. A minimum of 7 rows and 40 columns in the graphical display area is required for a single plot. On a 24 row by 80 column screen, two concurrent plots can be displayed. Larger screens accommodate more plots.When the cursor is placed on a plot (or bar graph) title, pressing either <Space> or the <Return> key removes the plot (or bargraph) from the graphical display area.
Pressing <C> clears whatever is in the upper-left corner of the graphical display area.
Scales for plots are determined by the maximum value contained in the history buffer at the time the plot is requested. If a later metric value is larger than the initial scale, the plot automatically re-scale to accommodate the larger value. Plots do not automatically re-scale to smaller values. Removing a plot and re-displaying it causes a new scale to be determined as above.
Displaying the bargraph
Use <B> to toggle on and off the display of the CPU consumption bar graph.Changing the sampling interval
The sampling interval can be set by an argument at invocation. The default sampling interval is two seconds. The sampling interval may be changed at any time by pressing either <+> or <->, which increments or decrements the interval by one second. The minimum sampling interval is one second. Users should note that a one second sampling interval places a moderate load on the system, and is not particularly useful for identifying system problems.Getting help
Press <?> to display the help screen in the text portion of the screen. Press <Esc> to return to the previous screen.Quitting rtpm
Press <Q> or <Ctrl><D> to exit rtpm.Accessing subscreens
Press <Space> or <Return> while the cursor is on a subscreen header to change the text-based metric display to the subscreen. Press <Esc> to return to the previous screen. Twelve subscreens are available from the top level screen:CPU
CALLS
MEMORY
PAGING
FILESYS
IO
TTY
QUEUE
LWPS
ETHER
TCP/IP
PAGING
PAGE IN
PAGE OUT/SWAPPING
FILESYS
FILE SYS CALLS
BUFFER CACHE
MISC/TABLES
IGETS/DIRBLKS
INODE RECLAIMS
ETHER
ETHERNET
INPUT ERRORS
OUTPUT ERRORS
TCP/IP
ICMP
TCP
IP
Display example
The default startup display looks like this:CPU 0 ====================================================------------------- CPU 1 ===------- CPU 2 - CPU 3 - total ============================------------ %s= _%u- |______________10|_ _ _ _ _2_0_|_ _ _ _ _3_0_|_ _ _ _ _4_0_|_ _ _ _ _5_0_|_ _ _ _ _6_0_|_ _ _ _ _7_0_|_ _ _ _ _8_0_|_ _ _ _ _9_0_|_ _ _ _1_0_0_|_In the default startup display, a bar graph of CPU utilization is displayed in the graphical portion of the screen. When rtpm is run on a multi-processor system, there is a bargraph for each CPU on the system and one for total CPU consumption. Systems with more than four processors require a screen size that contains more than 24 rows to display the entire bar graph. When rtpm is run on a small screen and is displaying statistics for a large multi-processor configuration, not all CPUs are displayed in the bar graph. A scroll bar at the left of the bar graph shows whether the bar graph can be scrolled up or down. The bar graph may be scrolled up and down with the <^> and <V> keys. In the CG view, the bar graph is displayed for CG-based CPU usage.CPU: CALLS/s: IO/s: QUEUE: TTY/s: ETHER: 58 %cpu 3460 calls 0 reads 1 runq 0 rcvs 1 xpkt/s 42 %usr 0 forks 0 rdblk 100 %run 0 xmit 1 rpkt/s 18 %sys 0 execs 0 writs 0 prunq 0 mdms 211 xoct/s 40 %int 20 reads 0 wrblk 0 %prun 0 canch 60 roct/s 0 %wio 2 writs 0 qlen 0 swpq 0 rawch 0 xerrs 42 %idl 0 Krwch 0 %busy 0 %swp 143 outch 496 rerrs
MEMORY: PAGING/s: FILESYS/s: LWPS: NETWARE: TCP/IP: 973 kma 0 pgins 0 igets 54 lwps 0 spx/s 2 tcp/s 10161 frmem 0 pgots 684 lkups 0 run 0 ipx/s 0 udp/s 32149 frswp 0 atchs 0 dirbk 52 sleep 0 sap/s 0 icmp/s 38 %mem 0 pflts 100 %dnlc 0 zomb 0 rip/s 2 ip/s 8 %swp 0 vflts 161 inode 30 procs 0 errs 1 errs
UNIX_SV lycia Thu Sept 1 16:04:11 1998 interval: 1 (1.00)
Pressing the <I> key when the CPU bargraph is displayed reports the percentage time spent processing interrupts; pressing <I> again turns off the display of interrupt data. Time spent in interrupt handling is represented by the <+> character as shown in the following display.
CPU 0 ====================================================++++++------------- CPU 1 ===------- CPU 2 - CPU 3 - total ============================+++--------- s= i+ u- |______________10|_ _ _ _ _2_0_|_ _ _ _ _3_0_|_ _ _ _ _4_0_|_ _ _ _ _5_0_|_ _ _ _ _6_0_|_ _ _ _ _7_0_|_ _ _ _ _8_0_|_ _ _ _ _9_0_|_ _ _ _1_0_0_|_
If the bargraph is cleared and the percentage cpu (usr+sys+int) time metric is plotted, the display looks like this:
%cpu total 100 80 |||| || |||| 60 ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| 40 ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| 20 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||Several plotting types are available by entering the <P> key; the above screen shows a vertical bar plot, and the following is an example of a scatter plot that consists of a single plotted point per sample.CPU: CALLS/s: IO/s: QUEUE: TTY/s: ETHER: 58 %cpu 3478 calls 0 reads 1 runq 0 rcvs 1 xpkt/s 42 %usr 0 forks 0 rdblk 100 %run 0 xmit 1 rpkt/s 15 %sys 0 execs 0 writs 0 prunq 0 mdms 291 xoct/s 43 %int 20 reads 0 wrblk 0 %prun 0 canch 154 roct/s 0 %wio 2 writs 0 qlen 0 swpq 0 rawch 0 xerrs 42 %idl 0 Krwch 0 %busy 0 %swp 223 outch 499 rerrs
MEMORY: PAGING/s: FILESYS/s: LWPS: NETWARE: TCP/IP: 974 kma 0 pgins 0 igets 56 lwps 0 spx/s 2 tcp/s 10814 frmem 0 pgots 687 lkups 0 run 0 ipx/s 0 udp/s 32113 frswp 0 atchs 0 dirbk 54 sleep 0 sap/s 0 icmp/s 34 %mem 0 pflts 100 %dnlc 0 zomb 0 rip/s 2 ip/s 8 %swp 0 vflts 162 inode 32 procs 0 errs 1 errs
UNIX_SV lycia Thu Sept 1 16:10:10 1998 interval: 1 (1.00)
%cpu total 100 * 80 ******************************************************************** ****** 60 40 20 0 ___________________________________________________________________________Accessing the LWP subscreen displays statistics about the number of processes and light weight processes, as well as some ps-like information about the LWPs that have run during the sampling interval. In this example, a runaway user process is consuming over half of the available CPU cycles:
% cpu total 100 80 ** 60 ************************************************ ************************* 40 20 0 ___________________________________________________________________________By default, the LWP subscreen displays all processes that have been active during the sampling period. Pressing <U> or <S> while the LWP subscreen is displayed limits the data to user or system processes, respectively. Pressing the <A> key reports all active user and system processes. The <e> key acts as a toggle switch: pressing <E> once displays all processes, including sleeping processes; pressing <E> again causes only active processes to be displayed. The keys can be used in combinations: pressing <A> and <E> will show all of the processes (including sleeping processes) that are on the system, pressing <U> and <E> will show all of the user processes, and pressing <S> and <E> will show all of the system processes. If more processes run during the sampling interval than will fit on the screen, the <<> and <>> keys can be used to scroll through the list.56 lwps 0 runnable lwps 0 zombie lwps 32 procs 2 lwps on CPU 54 sleeping lwps 0 idle lwps 400 procmax 0 lwpfail 0 stopped lwps 0 other lwps 0 procfail
%%% S USER PID LWPID CPU PRI CPUTIME SIZE TTY CMD[LWP] 51 O root 375 1 0 0 433:47.00 4339 ? runaway_proc 7 O root 728 1 1 53 2:52.24 4592 pts/3 ./rtpm 1 0 S root 0 23 1 79 0:25.77 0 ? sysproc[vx_inact_da 0 S root 0 19 1 79 0:00.23 0 ? sysproc[vx_inact_da 0 S root 0 2 1 79 4:02.75 0 ? sysproc[fsflushwp] 0 S root 0 14 1 79 2:12.47 0 ? sysproc[vx_flush_da
UNIX_SV lycia Thu Sept 1 16:28:18 1998 interval: 1 (1.00)
In the CG view, an extra column is added to the PS output to display the CG on which a lwp is executing.
On systems with a large number of CPUs, disks, or ethernet cards, the per-unit metrics associated with these resources may not fit on a small screen. When this happens, <-
, ->
, or <>
will be displayed at the right edge of the screen and the <<> and <>> keys can be used to scroll the per-resource metrics left and right. Moving the cursor off the edge of the screen also scrolls per-resource metrics.
Command summary
Cursor Motions
Changing Views
Plotting Metrics
Accessing Subscreens
Help
Locking rtpm into Memory
Bargraph
Changing the Sampling Interval
Scrolling Metrics
LWP Screen
Underscore Handling
Redraw
Exiting rtpm
Initialization file
When rtpm is invoked, it attempts to read the .rtpmrc initialization file from the user's home directory. If the .rtpmrc file is not found in the user's home directory, the system default /etc/.rtpmrc is used.The native language in which the .rtpmrc file is written is specified by the expression LANG=language, where language is a locale name describing the message catalog to be used for reading the initialization file. For example, setting LANG=C specifies the default English language strings as used in /etc/.rtpmrc. Note that setting LANG in the .rtpmrc file does not affect the messages displayed by rtpm.
The initialization file can be used to specify a default set of metrics to plot at initialization time, and also specifies the display colors for color terminals. Each line of the initialization file consists of a name, a colon, and an expression that specifies color or default plotting status.
The following display elements are specified in the initialization file:
background
default
plot
labels
headers
messages
bargraph
metric names
Color range expressions are used to assign display colors to ranges of metric values. A color range expression consists of a series of numbers, relational operators, and colors:
<color_range>:: <RANGE>[;<RANGE>] <RANGE>:: [<num><OP>]<color>[<OP><num><OP><color>]*[<OP><num>] <OP>:: < | <= | > | >= | == | !=For example
bargraph: 0 <= green < 60 <= yellow < 85 <= redsets the bargraph to green if CPU consumption is below 60%, yellow if it is between 60% and 85%, and red if it is greater than 85%.
Multiple expressions may be used, provided they are separated by semicolons. Since expressions are tested from left to right, the following expression is equivalent to the one above:
bargraph: green < 60 ; yellow < 85 ; redIn the text-based metric display area, the color assigned to default is used to display the numeric metric unless a color expression specifies otherwise. In the plot area, the color assigned to plot is used to display the plot characters unless a color expression specifies otherwise. In both the text-based and graphical display areas, if a color expression is true, the metric will be displayed in the color defined by the expression. Typically, colors will vary from green to yellow to red depending on the severity of a condition. On vertical bar chart plots, this will have the effect of several color bands, one above the other.
For metrics that indicate an alarm condition when they approach 0, such as free memory, the user may want to invert the plot so that 0 is displayed as the top of the y-axis as opposed to the bottom. Thus the plot will only display the alarm color under severe conditions.
To invert a plot, add the invert keyword to a metric in the initialization file:
freemem: 1000 >= yellow > 500 >= red ; invertPlot status expressions are used to specify metrics that are to be plotted when rtpm is invoked. Since metrics can be per-resource based, a metric is actually a set of values called instances. A metric has an instance for each resource (or combination of resources) on which it is based. For example, freemem is global, %usr time is kept per-CPU, and igets/s are kept both per-CPU and per-filesystem. Hence, there is one instance for freemem, n CPU instances for %usr, and n CPU * nfstyp instances for igets/s. A plot expression is used to specify the set of instances the user wants to plot. Here are some examples of plot expressions:
plot
plot(total)
plot(number)
plot(*)
plot(2, 3)
Usage note
On heavily loaded systems where memory is scarce, and especially with large screen sizes, rtpm may fail to allocate enough space to save all its history points. If this is the case, the history buffer size should be decreased using the -h option. On systems with ample memory, large display screens may benefit from increasing the history buffer size to the number of columns on the screen.List of metrics
The following is a list of all the metrics displayed by rtpm:Machine resource information
CPU
disk
fstype
fsnames
kmpool
kmasize
pgsz
dsname
nether
ethname
CPU consumption statistics
%cpu
%(wio+idl)
%usr
%sys
%int
%wio
%idl
Filesystem statistics
iget/s
dirblk/s
ipage/s
inopage/s
fswio
physwio
fltblinuse
fltblfail
fltblfail/s
flcktblmax
flcktbluse
flcktblfal
flcktblfail/s
flcktbl/s
maxinode
currinode
inodeinuse
inodefail
Memory statistics
freemem
freeswp
mem
balloc
ralloc
kmfail
kma(pg)
%mem
%memswp
%dskswp
dskswp
dskfreeswp
memswp
totalmem
Paging and swapping statistics
preatch/s
atch/s
atchfree/s
atfrpgot/s
atchmiss/s
pgin/s
pgpgin/s
pgout/s
pgpgout/s
swpout/s
ppgswpot/s
vpgswpot/s
swpin/s
pgswpin/s
virscan/s
virfree/s
physfree/s
pfault/s
vfault/s
sftlck/s
Process switching and queueing statistics
pswtch/s
runq
%runocc
swpq
%swpocc
prunq
%prunocc
System call statistics
syscall/s
fork/s
lwpcreat/s
exec/s
read/s
write/s
readch/s
writech/s
lookup/s
dnlchits/s
dnlcmiss/s
bread/s
bwrite/s
lread/s
lwrite/s
phread/s
phwrite/s
ipcmsgq/s
ipcsema/s
(rd+wrt)/s
(r+w)Kb/s
%dnlc
%rcache
%wcache
Terminal I/O statistics
rcvint/s
xmtint/s
mdmint/s
rawch/s
canch/s
outch/s
Process and LWP (Light weight process) statistics
procfail
procinuse
procmax
lwpfail
lwpinuse
lwpmax
lwp_sleep
lwp_run
lwp_idle
lwp_onproc
lwp_zombie
lwp_stop
lwp_other
lwp_total
lwp_nproc
Disk statistics
The following statistics are given for each disk. Pressing <Enter>, or the space bar, on a disk header gives the statistics for the individual slices of that disk.instqlen
%busy
avgqlen
dsread/s
dsrblk/s
dswrit/s
dswblk/s
STREAMS statistics
streams
queues
mdbblks
msgblks
links
events
eventfail
Ethernet statistics
InUcastPkts/s
OutUcastPkts/s
InNUcastPkts/s
OutNUcastPkts/s
InOctets/s
OutOctets/s
InErrors
etherAlignErrors
etherCRCerrors
etherOverrunErrors
etherUnderrunErrors
etherMissedPkts
InDiscards
etherReadqFull
etherRcvResources
etherCollisions
OutDiscards
OutErrors
etherAbortErrors
etherCarrierLost
OutQlen
General networking statistics
ip_sum/s
icmp_sum/s
udp_sum/s
tcp_sum/s
neterr_sum
neterr_sum/s
IP (Internet protocol) networking statistics
ip_total/s
ip_badsum
ip_tooshort
ip_toosmall
ip_badhlen
ip_badlen
ip_unknownproto
ip_fragments
ip_fragdropped
ip_fragtimeout
ip_reasms
ip_forward
ip_cantforward
ip_noroutes
ip_redirectsent
ip_inerrors
ip_indelivers/s
ip_outrequests/s
ip_outerrors
ip_pfrags
ip_frags
ip_fragfails
Internet Control Message Protocol (ICMP networking statistics
icmp_intotal/s
icmp_outtotal/s
icmp_reflect/s
icmp_outerrors
icmp_error
icmp_oldicmp
icmp_badcode
icmp_tooshort
icmp_checksum
icmp_badlen
icmp_echo_reply_in
icmp_echo_reply_out
icmp_dest_unreachable_in
icmp_dest_unreachable_out
icmp_source_quench_in
icmp_source_quench_out
icmp_routing_redirects_in
icmp_routing_redirects_out
icmp_echo_in
icmp_echo_out
icmp_time_exceeded_in
icmp_time_exceeded_out
icmp_parameter_problems_in
icmp_parameter_problems_out
icmp_time_stamp_in
icmp_time_stamp_out
icmp_time_stamp_reply_in
icmp_time_stamp_reply_out
icmp_info_request_in
icmp_info_request_out
icmp_info_reply_in
icmp_info_reply_out
icmp_address_mask_request_in
icmp_address_mask_request_out
icmp_address_mask_reply_in
icmp_address_mask_reply_out
Transport Control Protocol (TCP) networking statistics
tcp_sndtotal/s
tcp_sndpack/s
tcp_sndbyte/s
tcp_sndrexmitpack
tcp_sndrexmitbyte
tcp_sndacks
tcp_delack
tcp_sndurg
tcp_sndprobe
tcp_sndwinup
tcp_sndctrl
tcp_rcvtotal/s
tcp_rcvackpack/s
tcp_rcvackbyte/s
tcp_rcvdupack
tcp_rcvacktoomuch
tcp_rcvpack
tcp_rcvbyte
tcp_rcvduppack
tcp_rcvdupbyte
tcp_rcvpartduppack
tcp_rcvpartdupbyte
tcp_rcvoopack
tcp_rcvoobyte
tcp_rcvpackafterwin
tcp_rcvbyteafterwin
tcp_rcvwinprobe
tcp_rcvwinupd
tcp_rcvafterclose
tcp_rcvbadsum
tcp_rcvbadoff
tcp_rcvshort
tcp_connattempt
tcp_accepts
tcp_connects
tcp_closed
tcp_drops
tcp_conndrops
tcp_rttupdated
tcp_segstimed
tcp_rexmttimeo
tcp_timeoutdrop
tcp_persisttimeo
tcp_keeptimeo
tcp_keepprobe
tcp_keepdrops
User Datagram Protocol (UDP) networking statistics:
udp_hdrops
udp_badlen
udp_badsum
udp_fullsock
udp_noports
udp_indelivers/s
udp_inerrors
udp_outtotal/s
© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 25 April 2004
<!-- NAVEND -->
相关推荐
UnixWare 7 Release 7.1.3是一款经过优化和改进的UNIX操作系统版本,特别适合对稳定性、安全性和性能有较高要求的企业级应用环境。通过正确的注册码输入,用户可以合法地激活并使用该系统的所有功能。了解这些基本...
标题和描述均提到了"Unixware 7 non-stop 集群",这指向了Unixware 7系统下的非停止集群技术。Unixware 7是一款由SCO集团开发的Unix操作系统,其非停止集群技术(NonStop Clusters)是用于提高系统可用性、可管理性...
SCO UnixWare 7.x Introduction: ------------- This document describes the procedure to install the SCO UnixWare 7 driver for 10/100M PCI Fast Ethernet Adapter. Location of Driver: \uw7\rtspkg....
SCO UnixWare配置及参数修改 SCO UnixWare裸设备建立
在本文中,我们将深入探讨如何在Unixware操作系统上安装Sybase数据库管理系统。Sybase是一款强大的企业级数据库解决方案,广泛应用于各种Unix环境,包括Unixware。Unixware 7.1.1是SCO公司提供的一个稳定且功能丰富...
【Unixware 7.1.1 全面学习资料】是针对Unixware操作系统的一个详细教程,特别是关于7.1.1版本的安装过程。Unixware是由Novell公司开发的一种UNIX操作系统,广泛应用于服务器和工作站环境。以下是安装Unixware 7.1.1...
UnixWare学习资料主要关注的是在银行核心平台中广泛使用的操作系统UnixWare及其相关的中间件技术。中间件在银行系统中扮演着关键角色,它连接并协调不同的应用系统,确保数据的高效传输和业务流程的顺畅进行。在这个...
【tmake使用指南】 tmake是一款由Trolltech公司开发的Perl语言编写的工具,主要用于生成和管理makefile,尤其适用于Qt开发。它简化了makefile的创建过程,使得开发者无需深入理解autoconf等复杂工具即可快速生成...
- 使用AIX系统的环境下,可以通过命令行工具或图形界面工具完成备份。 - **1.2 Unixware环境** - 对于使用Unixware的环境,也可以通过相应的工具进行备份操作。 **2. 文件系统备份** - **2.1 AIX环境** - AIX...
本文档提供了s-numen核心防护系统的安装使用说明,包括安装指南、系统要求、安装过程、配置文件目录结构等详细信息,以便帮助用户正确地安装和配置s-numen核心防护系统。 安装指南 s-numen核心防护系统可以在多种...
* 多种操作系统:Windows、HP-UX、Sun Solaris、Linux、IBM AIX、IBM MVS、Novell NetWare、Compaq Tru64 UNIX、FreeBSD、SCO UnixWare、SGI IRIX、Windows 3.1、Windows NT for Alpha、IBM OS/2 Chariot 的使用...
Webmin是目前功能最强大的基于Web的Unix系统管理工具。管理员通过浏览器访问Webmin的各种管理功能并完成相应的管理动作。目前Webmin支持绝大多数的Unix系统,这些系统除了各种版本的linux以外还包括:AIX、HPUX、...
Webmin是目前功能最强大的基于Web的Unix系统管理工具。管理员通过浏览器 访问Webmin的各种管理功能并完成相应的管理动作。目前Webmin支持绝大多数的Unix系统,这些系统除了各种版本的linux以为还包 括:AIX、HPUX、...
Linux操作系统的核心是Linux内核,但由于它通常会搭配使用GNU工程的各种工具和库,因此人们常把基于Linux内核并且使用GNU工具的操作系统统称为Linux系统。 Linux的发展历史源远流长,它的起源可以追溯到UNIX操作...
本文介绍了一个基于UNIX类操作系统的紧密结构地震台网中心核心数据处理系统,该系统适用于数字地震台网中心,具备高实时性、高可靠性以及广泛适应性等特点,能够支持地震预警在内的实时地震数据应用需求。...
同时,检查UnixWare7.1.1的版本兼容性,确保操作系统能够支持Oracle的运行。 接下来,创建用于安装的Oracle用户账号。在X-WINDOWS环境下,通过SCO Admin的Account Manager创建名为`oracle`的新用户,并设置相应的...
作为超级用户(root),你需要登录UnixWare系统,并为本机分配一个IP地址,这可以通过Scoadmin工具来完成。接着,创建名为“sybase”的用户组和同名用户,分配相应的权限,如group:sybase 和 user:sybase。 在环境...
**1.2 UnixWare 7** - **Oracle 8 安装步骤**: - 下载并解压安装包。 - 运行安装脚本。 - 配置初始化参数文件`init.ora`。 - 启动数据库服务并进行基本测试。 **1.3 HP-UX** - **Oracle 8 安装步骤**: - ...