OSF physical memory, good reference
list David Gore
Henrik, This is a good page the Rosetta Stone for UNIX. I was looking to find out how I could determine physical memory on an OSF host, so you could include the memory test for OSF? Here is where I was looking: http://bhami.com/rosetta.html And here is the command I used to determine physical memory (could have read the man page for vmstat): # vmstat -P Total Physical Memory = 5120.00 M = 655360 pages Physical Memory Clusters: start_pfn end_pfn type size_pages / size_bytes 0 256 pal 256 / 2.00M 256 655349 os 655093 / 5117.91M 655349 655360 pal 11 / 88.00k Physical Memory Use: start_pfn end_pfn type size_pages / size_bytes 256 277 unixtable 21 / 168.00k 277 284 scavenge 7 / 56.00k 284 855 text 571 / 4.46M 855 983 data 128 / 1.00M 983 1149 bss 166 / 1.30M 1149 1312 kdebug 163 / 1.27M 1312 1320 cfgmgmt 8 / 64.00k 1320 1321 locks 1 / 8.00k 1321 2391 unixtable 1070 / 8.36M 2391 2404 pmap 13 / 104.00k 2404 12955 vmtables 10551 / 82.43M 12955 655349 managed 642394 / 5018.70M ============================ Total Physical Memory Use: 655093 / 5117.91M Managed Pages Break Down: free pages = 499488 active pages = 4218 inactive pages = 13501 wired pages = 35695 ubc pages = 89530 ================== Total = 642432 WIRED Pages Break Down: vm wired pages = 3335 ubc wired pages = 19570 meta data pages = 6550 malloc pages = 4529 contig pages = 652 user ptepages = 824 kernel ptepages = 215 free ptepages = 9 ================== Total = 35684 -- David Gore (v965-3670) Enhanced Technology Support (ETS) Network Management Systems (NMS) IMPACT Transport Team Lead - SCSA, SCNA Page: 1-800-PAG-eMCI pin 1406090 Vnet: 965-3676
list Henrik Størner
▸
On Sun, Aug 07, 2005 at 03:47:35AM +0000, David Gore wrote:
Henrik, This is a good page the Rosetta Stone for UNIX. I was looking to find out how I could determine physical memory on an OSF host, so you could include the memory test for OSF? Here is where I was looking: http://bhami.com/rosetta.html
This is great. I've actually used this some time ago, but had forgotten about it.
▸
And here is the command I used to determine physical memory (could have read the man page for vmstat): # vmstat -P
Could you send me the output from "swapon -s" also, so I can include the swap info as well ? Thanks, Henrik
list Anton Burkhalter
Henrik,
here is a script which produces the following output on Tru64 V5.1B
hobbit at hifpxx31 $ ./memory.sh
... ... "status myhost,my,domaine.memory green Sun Aug 7 10:02:54 MEST
2005 Memory OK
Memory Used Total Percentage
&green Physical 1951M 2048M 95%
&green Swap 1553M 8192M 18% "
--------------------------vvvvvvv--------------------------
#!/bin/ksh
################################################################################
##### Environment settings
#####
## The following two values could be overwritten by
$HCHOME/etc/common-def.sh
#
PERCENT_PHYS_WARN="100" # go yellow at this level
PERCENT_PHYS_PANIC="101" # go red and page at this level
PERCENT_SWAP_WARN="80" # go yellow at this level
PERCENT_SWAP_PANIC="90" # go red and page at this level
MyP1=$1
MyFCT=memory
ScriptName=`basename $0`; export ScriptName
HCHOME=/usr/local/hobbit/client
. $HCHOME/etc/common-def.sh
MEMDATA=$HCHOME/tmp/memdata.tmp.$$
SWAPDATA=$HCHOME/tmp/swapdata.tmp.$$
MyAGENT=`hostname | sed "s/\./,/g"`
MyAGENT=`echo ${MyAGENT}.${MyFCT}"`
### --
################################################################################
##### Functions
#####
get_status()
{
COLOR="green"
STATUS="Memory OK"
/usr/bin/rm -f $MEMDATA
/usr/bin/rm -f $SWAPDATA
# initialize result values
PHYS_MEMORY=0
PHYS_MEMORY_USED=-1
SWAP_MEMORY=0
SWAP_MEMORY_USED=-1
/usr/bin/vmstat -P >$MEMDATA
/sbin/swapon -s >$SWAPDATA
PHYS_MEMORY=`cat $MEMDATA | grep "Total Physical Memory" | awk {'print
$5'} | head -1 | cut -d. -f1`
PHYS_MEMORY_KB=`expr $PHYS_MEMORY \* 1024`
PHYS_MEMORY_FREE_PAGES=`cat $MEMDATA | grep "free pages" | awk {'print $4'}`
PHYS_MEMORY_FREE_KB=`expr $PHYS_MEMORY_FREE_PAGES \* 8`
PHYS_MEMORY_USED_KB=`expr $PHYS_MEMORY_KB - $PHYS_MEMORY_FREE_KB`
PHYS_MEMORY_USED=`expr $PHYS_MEMORY_USED_KB / 1024`
SWAP_MEMORY_PAGES=`cat $SWAPDATA | grep "Allocated space:" | awk {'print
$3'} | tail -1`
SWAP_MEMORY=`expr $SWAP_MEMORY_PAGES \* 8 / 1024`
SWAP_MEMORY_USED_PAGES=`cat $SWAPDATA | grep "In-use space:" | awk
{'print $3'} | tail -1`
SWAP_MEMORY_USED=`expr $SWAP_MEMORY_USED_PAGES \* 8 / 1024`
if [ $PHYS_MEMORY -eq 0 ]; then
exit 0
fi
# percentage of memory used
PERCENT_PHYS_MEMORY_USED=0
PERCENT_SWAP_MEMORY_USED=0
if [ $PHYS_MEMORY -gt 0 ]; then
PERCENT_PHYS_MEMORY_USED=`expr 100 \* $PHYS_MEMORY_USED / $PHYS_MEMORY`
fi
if [ $SWAP_MEMORY -gt 0 ]; then
PERCENT_SWAP_MEMORY_USED=`expr 100 \* $SWAP_MEMORY_USED / $SWAP_MEMORY`
fi
# calculate physical memory usage
if [ $PHYS_MEMORY_USED -ge 0 ]; then
if [ $PERCENT_PHYS_MEMORY_USED -ge $PERCENT_PHYS_PANIC ]; then
COLOR="red"
PHYS_COLOR="red"
STATUS="Memory **very** low"
else
if [ $PERCENT_PHYS_MEMORY_USED -ge $PERCENT_PHYS_WARN ]; then
PHYS_COLOR="yellow"
if [ "$COLOR" != "red" ]; then
COLOR="yellow"
STATUS="Memory low"
fi
else
PHYS_COLOR="green"
fi
fi
else
PHYS_COLOR="clear"
fi
# virtual memory usage
if [ $SWAP_MEMORY_USED -ge 0 ]; then
if [ $PERCENT_SWAP_MEMORY_USED -ge $PERCENT_SWAP_PANIC ]; then
COLOR="red"
SWAP_COLOR="red"
STATUS="Memory **very** low"
else
if [ $PERCENT_SWAP_MEMORY_USED -ge $PERCENT_SWAP_WARN ]; then
SWAP_COLOR="yellow"
if [ "$COLOR" != "red" ]; then
COLOR="yellow"
STATUS="Memory low"
fi
else
SWAP_COLOR="green"
fi
fi
else
STATUS="--"
SWAP_COLOR="clear"
fi
echo "$STATUS"
echo " Memory Used Total Percentage"
if [ ! "$PHYS_COLOR" = "clear" ]; then
echo "&${PHYS_COLOR} Physical ${PHYS_MEMORY_USED}M ${PHYS_MEMORY}M
${PERCENT_PHYS_MEMORY_USED}%" | \
awk '{printf "%s %-9s %8s %8s %12s\n",$1,$2,$3,$4,$5}'
else
echo "&${PHYS_COLOR} Unable to calculate virtual memory usage"
fi
if [ ! "$SWAP_COLOR" = "clear" ]; then
echo "&${SWAP_COLOR} Swap ${SWAP_MEMORY_USED}M ${SWAP_MEMORY}M
${PERCENT_SWAP_MEMORY_USED}%" | \
awk '{printf "%s %-9s %8s %8s %12s\n",$1,$2,$3,$4,$5}'
else
echo "&${SWAP_COLOR} Unable to calculate virtual memory usage"
fi
/usr/bin/rm -f $MEMDATA
/usr/bin/rm -f $SWAPDATA
}
/usr/bin/rm -f $HCHOME/tmp/$MyAGENT
touch $HCHOME/tmp/$MyAGENT
get_status > $HCHOME/tmp/$MyAGENT
MyDATE=`/bin/date "+%Y-%m-%d %H:%M"`
### Send the result to all Hobbit display servers
#
# debug version, do not send it ...
echo "... ... \"status $MyAGENT $COLOR `date` `cat
$HCHOME/tmp/$MyAGENT` \""
#/usr/bin/rm -f $FDMDATA
exit
-------------------------------^^^^^^^^^^^^^^^^^^^^^^^-------------------
I use the following function to get processor load informations.
--------------------------vvvvvvvvvvvvvvvvvvvvvvvvvvvvv---------------------
get_status()
{
COLOR="green"
set `uptime | awk '{ gsub(/,/,""); printf "%s %s
%s\n",$(NF-2),$(NF-1),$NF}'`
AVG1=$1
AVG5=$2; export AVG5
AVG15=$3
NRPROC=`ps -ef | wc -l | sed "s/ //g"`; export NRPROC
# The Hobbit "do_la.c" requires a line like "up: 36 days, 6 users, 239
procs, load=0.72"
uptime | awk '{printf "%s: %s %s %s %s %3s procs,
load=%s\n",$2,$3,$4,$(NF-6),$(NF-5),ENVIRON["NRPROC"],ENVIRON["AVG5"]}'
### set condition red yellow green
echo "LOAD average on `hostname` is:"
echo ""
echo " over the last 60 seconds : ${AVG1}"
echo " over the last 5 minutes : ${AVG5}"
echo " over the last 15 minutes : ${AVG15}"
COLOR=`echo "$AVG5 $CPUWARN $CPUPANIC" | awk '{ $1 < $2 ? x="green" : $1
< $3 ? x="yellow" :x="red"; print (x)}'`
}
--------------------------^^^^^^^^^^^^^^^^^^^^^^^^^--------------------------
Regards,
Tony
list Henrik Størner
▸
On Sun, Aug 07, 2005 at 10:24:35AM +0200, Anton Burkhalter wrote:
Henrik, here is a script which produces the following output on Tru64 V5.1B hobbit at hifpxx31 $ ./memory.sh ... ... "status myhost,my,domaine.memory green Sun Aug 7 10:02:54 MEST 2005 Memory OK Memory Used Total Percentage &green Physical 1951M 2048M 95% &green Swap 1553M 8192M 18% "
Thanks, but I'd really like to see what the "swapon -s" output looks like. This script works fine for a client that generates the status messages itself, but it's too heavy for the Hobbit client design. (My idea with the Hobbit client is to have as little "intelligence" in the client as possible - I prefer to do very little processing of the data on the client, and just forward all of the raw output to the Hobbit server. That lets the admin see exactly what the system says about itself - sometimes these commands report things that don't show up in the interpreted data used for the Hobbit status messages. E.g. the "vmstat -P" output on OSF has a detailed break-down of how the memory is used, which might be useful when you get a memory-alert and need to know WHY all of the memory is gone. Instead of having to login to the box and run commands to figure it out, you can dig into the raw client-data which is available directly in Hobbit, and get the information you need. The fact that it also lets you centralize the alert configuration and potentially do some event correlation between different systems is just an added bonus). Regards, Henrik
list Anton Burkhalter
Ok, here we are :
osadmin at test1> swapon -s
Swap partition /dev/disk/dsk0b:
Allocated space: 1572864 pages (12.00GB)
In-use space: 51996 pages ( 3%)
Free space: 1520868 pages ( 96%)
Total swap allocation:
Allocated space: 1572864 pages (12.00GB)
In-use space: 51996 pages ( 3%)
Available space: 1520868 pages ( 96%)
osadmin at test1 #
osadmin at test2> swapon -s
Swap partition /dev/disk/dsk1b:
Allocated space: 1048576 pages (8.00GB)
In-use space: 199699 pages ( 19%)
Free space: 848877 pages ( 80%)
Total swap allocation:
Allocated space: 1048576 pages (8.00GB)
In-use space: 199699 pages ( 19%)
Available space: 848877 pages ( 80%)
osadmin at test2>
osadmin at test3> swapon -s
Swap partition /dev/disk/dsk3b:
Allocated space: 868544 pages (6.63GB)
In-use space: 8998 pages ( 1%)
Free space: 859546 pages ( 98%)
Swap partition /dev/disk/dsk7c:
Allocated space: 901440 pages (6.88GB)
In-use space: 9136 pages ( 1%)
Free space: 892304 pages ( 98%)
Total swap allocation:
Allocated space: 1769984 pages (13.50GB)
In-use space: 18134 pages ( 1%)
Available space: 1751850 pages ( 98%)
osadmin at test3>
osadmin at test4> swapon -s
Swap partition /dev/disk/dsk3b:
Allocated space: 868544 pages (6.63GB)
In-use space: 126384 pages ( 14%)
Free space: 742160 pages ( 85%)
Swap partition /dev/disk/dsk6c:
Allocated space: 901440 pages (6.88GB)
In-use space: 125968 pages ( 13%)
Free space: 775472 pages ( 86%)
Swap partition /dev/disk/dsk7c:
Allocated space: 901440 pages (6.88GB)
In-use space: 125603 pages ( 13%)
Free space: 775837 pages ( 86%)
Total swap allocation:
Allocated space: 2671424 pages (20.38GB)
In-use space: 377955 pages ( 14%)
Available space: 2293469 pages ( 85%)
osadmin at test4>
osadmin at test5> swapon -s
Swap partition /dev/disk/dsk5b:
Allocated space: 868544 pages (6.63GB)
In-use space: 108247 pages ( 12%)
Free space: 760297 pages ( 87%)
Swap partition /dev/disk/dsk8c:
Allocated space: 901440 pages (6.88GB)
In-use space: 108482 pages ( 12%)
Free space: 792958 pages ( 87%)
Total swap allocation:
Allocated space: 1769984 pages (13.50GB)
In-use space: 216729 pages ( 12%)
Available space: 1553255 pages ( 87%)
osadmin at test5>
Regards,
Tony
▸
Thanks, but I'd really like to see what the "swapon -s" output looks like. This script works fine for a client that generates the status messages itself, but it's too heavy for the Hobbit client design. (My idea with the Hobbit client is to have as little "intelligence" in the client as possible - I prefer to do very little processing of the data on the client, and just forward all of the raw output to the Hobbit server. That lets the admin see exactly what the system says about itself - sometimes these commands report things that don't show up in the interpreted data used for the Hobbit status messages. E.g. the "vmstat -P" output on OSF has a detailed break-down of how the memory is used, which might be useful when you get a memory-alert and need to know WHY all of the memory is gone. Instead of having to login to the box and run commands to figure it out, you can dig into the raw client-data which is available directly in Hobbit, and get the information you need. The fact that it also lets you centralize the alert configuration and potentially do some event correlation between different systems is just an added bonus). Regards, Henrik
list David Gore
Unfortunately we are on Tru64 4.x
user-c85fc2ceea18@xymon.invalid:/some/file/system> swapon -s
Swap partition /dev/rz25b (default swap):
Allocated space: 64000 pages (500MB)
In-use space: 1 pages ( 0%)
Free space: 63999 pages ( 99%)
Swap partition /dev/rz18b:
Allocated space: 256000 pages (2000MB)
In-use space: 1 pages ( 0%)
Free space: 255999 pages ( 99%)
Swap partition /dev/rz10b:
Allocated space: 64000 pages (500MB)
In-use space: 1 pages ( 0%)
Free space: 63999 pages ( 99%)
Total swap allocation:
Allocated space: 384000 pages (3000MB)
Reserved space: 28050 pages ( 7%)
In-use space: 3 pages ( 0%)
Available space: 355950 pages ( 92%)
user-c85fc2ceea18@xymon.invalid:/some/file/system> uname -a
OSF1 rsoimpm1.mcilink.com V4.0 1229 alpha
It does appear that most of our hosts do not have the 'Reserved space'
line, but otherwise it is similar to Anton's output. I have included
the man page in case you were interested.
David
-------------- next part --------------
swapon(8) swapon(8)
NAME
swapon - Specifies additional file for paging and swapping
SYNOPSIS
/sbin/swapon [-asv] [-p priority] [-l lowsize] [-h highsize] filename
DESCRIPTION
The swapon command is used to specify additional paging files. A paging
file can be a block special device. (Digital UNIX does not currently sup-
port paging and swapping to a regular file. All swapping and paging areas
must be block special devices.) The swapon command uses a priority default
of 4 for block special devices. Calls to swapon normally occur in the sys-
tem multiuser state initialization.
When you make more swap space available with the swapon command, the addi-
tional swap space is available until the system is rebooted. To make addi-
tional swap space permanent, you must specify the swap file entry in the
/etc/fstab file.
The swapon command flags can override the partition specifications in the
/etc/fstab file.
(Because Digital UNIX does not currently support paging and swapping to a
regular file, the -p option is not supported.) The -p flag specifies the
priority of the paging file. When the kernel looks for a paging file, it
pages to the highest priority file that is available. If the file is una-
vailable, it tries a file of the next highest priority, and so on until it
finds a file onto which it can page. (A file becomes unavailable when it
has no more space.) Priorities are 0, 1, 2, 3, 4, with 0 being lowest
priority, and 4 being highest priority. Multiple paging files can have the
same priority. For example, there can be two files installed at priority 4.
Files of the same priority are paged out to in a round-robin fashion to
balance their usage.
(Because Digital UNIX does not currently support paging and swapping to a
regular file, the -l and -h options are not supported.) The -l option is
used to specify the low water mark. Normally, the -a option is used, caus-
ing all files marked as sw (swap files) in the /etc/fstab file to be made
available. The -h option is used to specify the high water mark. The
operating system will not expand the paging file to be larger than the high
water mark. If the paging file grows larger than the low water mark, and
then shrinks below the low water mark, the operating system will not make
the file smaller than the low water mark. If the low water mark is set to
0, then the paging file will not shrink after paging space is freed. The
default value for the low water mark is 20Mbytes; the default value for the
high water mark is unlimited.
You can use Logical Storage Manager (LSM) volumes for additional swap
space. For high system availability, you can mirror the LSM volumes. The
Logical Storage Manager manual describes how to use the swapon command to
configure an LSM mirrored volume as additional swap space.
There are two strategies for swap space allocation: immediate mode and
deferred or over-commitment mode. The two strategies differ in the point
in time at which swap space is allocated. If immediate mode is used, swap
space is allocated when modifiable virtual address space is created. If
deferred mode is used, swap space is not allocated until the system needs
to write a modified virtual page to swap space. Immediate mode is the
default swap space allocation strategy.
Immediate mode is more conservative than deferred mode because each modifi-
able virtual page is assigned a page of swap space when it is created. If
you use the immediate mode of swap space allocation, you must allocate a
swap space that is at least as large as the total amount of modifiable vir-
tual address space that will be created on your system. Immediate mode
requires significantly more swap space than deferred mode because it
guarantees that there will be enough swap space if every modifiable virtual
page is modified.
If you use the deferred mode of swap space allocation, you must estimate
the total amount of virtual address space that will be both created and
modified, and compare that total amount with the size of your system's phy-
sical memory. If this total amount is greater than the size of physical
memory, the swap space must be large enough to hold the modified virtual
pages that do not fit into your physical memory. If your system's workload
is complex and you are unable to estimate the appropriate amount of swap
space by using this mode, you should first use the default amount of swap
space and adjust the swap space as needed.
To determine which swap space allocation mode is being used, check for the
existence of a soft link named /sbin/swapdefault, which points to the pri-
mary swap partition. If the /sbin/swapdefault file exists, the system uses
the immediate mode for swap space allocation. To enable the deferred mode,
rename or delete this soft link.
If the /sbin/swapdefault file does not exist and you want to use the
immediate mode of swap space allocation, become superuser and create the
file by using the following command syntax:
ln -s /dev/rzxy /sbin/swapdefault
The x variable specifies the device number for the device that holds the
primary swap partition, and the y variable specifies the swap partition.
Usually, the swap device number is the same as the boot device number, and
the primary swap partition is partition b.
You must reboot the system for the new mode to take effect.
FLAGS
-a Installs all paging files specified in the /etc/fstab file.
-h highsize
The high water mark. Currently not supported.
-l lowsize
The low water mark. Currently not supported.
-p priority
The priority of the specified paging file. Currently not sup-
ported.
-s Displays swap space utilization. For each swap partition, this
flag displays the total amount of allocated swap space, the
amount of swap space that is being used, and the amount of free
swap space.
-v Generates verbose output.
NOTES
There is no way to stop paging and swapping on a file. It is therefore not
possible to use swap files that can be dismounted during system operation.
The new -p flag replaces earlier versions of the -p flag, which caused the
swapon command to designate the paging file as a preferred paging file.
EXAMPLES
The following example shows a swap file entry in an /etc/fstab file:
/dev/rz0b swap2 ufs sw 0 0
The following command adds the /dev/rz0b block device file as swap space:
swapon /dev/rz0b
ERRORS
You may receive the following messages when using the swapon command:
+ special-device or an overlapping partition is open.
Quitting...
This message indicates that you tried to add a partition as a swap
device that is actively in use by UFS, AdvFS, swap, or LSM.
+ special-device is marked in use for fstype in the disklabel.
If you continue with the operation you can possibly destroy existing
data.
CONTINUE? [y/n]
This message indicates that you tried to use a partition as a swap
device that is not currently in active use but is marked for use in
the disk label's partition map. For example, the partition may be
part of an LSM volume or an AdvFS domain.
If you know that the partition you specified to swapon does not con-
tain any data, you can choose to override the warning. In this case,
the fstype in the disk label will be modified to swap.
Note that you can use the disklabel -s command to set the fstype in
the disk label to unused for partitions that do not contain any valid
data. See disklabel(8) for more information.
+ Partition(s) which overlap special-device are marked in use.
If you continue with the operation you can possibly destroy existing
data.
CONTINUE? [y/n]
This message indicates that the partition you specified is not marked
for use, but other, overlapping partitions on the disk are marked for
use. If you override this warning, the fstype in the disk's label
will be modified. The partition you specified to swapon will be
marked as in use as a swap device and all overlapping partition will
be marked UNUSED.
The following examples illustrate these messages:
1. Adding a partition that is marked for use as a swap device:
# /usr/sbin/swapon /dev/rz11g
/dev/rz11g disk is marked in use for LSMpubl in the disklabel.
If you continue with the operation you can possibly destroy
existing data.
CONTINUE? [y/n]
Partition g of disk rz11 is part of a disk marked for use by LSM. If
LSM is not actively using this partition and the partition does not
contain any data, you may want to override this warning, by answering
y. In this case, partition g will be marked as swap in the disk
label.
2. Adding a partition as a swap device whose overlapping partitions are
marked for use:
# /usr/sbin/swapon /dev/rz11c
Partition(s) which overlap /dev/rz11c are marked in use.
If you continue with the operation you can possibly destroy
existing data.
CONTINUE? [y/n]
If you answer yes, partition c on disk rz11 will be marked swap in the
disk label and all partitions that overlap c will be marked UNUSED.
3. Adding a partition which is currently in use as a swap device:
# /usr/sbin/swapon /dev/rz11g
/dev/rz11g or an overlapping partition is open.
Quitting...
4. Adding a partition which does not have a disk label as a swap device:
# /usr/sbin/swapon /dev/rz11c
The disklabel for /dev/rz11c does not exist or is corrupted.
Quitting...
See disklabel(8) for information on installing a disk label on a disk.
FILES
/sbin/swapon
Specifies the command path
/etc/fstab
Specifies information about file systems and swap files.
/sbin/swapdefault
Specifies the primary swap partition and indicates that the
immediate mode of swap space allocation is being used.
RELATED INFORMATION
Functions: swapon(2)
System Administration
-------------- next part --------------
vmstat(1) vmstat(1)
NAME
vmstat - Displays virtual memory statistics
SYNOPSIS
vmstat interval [count]
vmstat [-f|-M|-P|-s]
The vmstat command displays system statistics for virtual memory,
processes, trap, and CPU activity.
OPTIONS
-f Displays only statistics about the number of forks since system startup
(see the fork() call).
-M Displays information about memory usage by buckets. This information
can be used for kernel debugging.
-P Displays the following accumulated statistics about physical memory
use:
Total Physical Memory
Number of megabytes of installed memory, and the equivalent page
value.
Physical Memory Clusters
How physical memory is clustered. The starting and ending page
frames (pfn) and where the memory is utilized (pal, os, and
*nvram).
Physical Memory Use
A breakdown of memory usage by os, the starting and ending page
frames, type of usage such as unixtable, or bss and the total phy-
sical memory in use.
Managed Pages Break Down
A snapshot of where managed physical memory resided when the vmstat
command executed. The display shows the number of pages in the
free queue, active and inactive pages, wired pages and unified
buffer cache (ubc) pages.
WIRED Pages Break Down
A further breakdown of physical pages that are wired in memory.
The display typically shows:
• vm and ubc wired pages
• meta data, malloc, and contig pages
• user, kernel, and free ptepages.
-s Displays the following accumulated statistics along with the page size:
active pages
Total number of pages that are currently in use but can be used for
paging.
inactive pages
Total number of VM pages that are allocated but are most likely to
be used for paging.
free pages
Total number of unreferenced (clean) pages that are available for
use.
wire pages
Total number of pages that are currently in use and cannot be used
for paging (not a real list).
virtual memory page faults
Number of address translation faults that have occurred.
copy-on-write page faults
Number of copy-on-write page faults, which occur if the requested
page is shared by a parent process and one or more child processes
(using the fork function) and if one of the processes needs to
modify the page. In this case, VM loads a new address into the
translation buffer and copies the contents of the requested page
into the new address for modification by the process.
zero file page faults
Number of zero-filled-on-demand page faults, which occur if VM can-
not find the page in the internal data structures and if the
requested page is new and has never been referenced. In this case,
VM initializes a physical page (the contents of the page are zeroed
out) and loads the address into the page table.
reattaches from reclaim list
Number of pages that have been faulted while on the inactive list.
pages paged in
Number of requests for pages from a pager.
pages paged out
Number of pages that have been paged out.
task and thread context switches
Number of task and thread context switches per second.
device interrupts
Number of nonclock device interrupts per second.
system calls
Number of system calls called per second.
DESCRIPTION
If you specify interval, vmstat displays the statistics listed below every
interval seconds. The first report is for all time since a reboot, and
each subsequent report is for the last interval only. If you specify count
after interval, count specifies the number of reports. For example, vmstat
1 10 produces 10 reports at 1-second intervals. You cannot specify count
without interval, since the first numeric argument to vmstat is always
assumed to be interval.
At any time, system memory can be in use by the kernel in kseg, wired
(pages that are currently in use and cannot be used for paging), on the
active list (pages that are currently in use but can be used for paging),
on the inactive list (pages that are allocated but are most likely to be
used for paging), on the free list (pages that are clean and available for
use), or used by the Unified Buffer Cache (UBC). The vmstat command does
not report on the memory in kseg and memory used by the UBC.
The following values are displayed:
Process information:
r Number of threads that are running or are runnable.
w Number of threads waiting interruptibly.
u Number of threads waiting uninterruptibly.
Virtual memory information:
act Total number of pages on the active list, the inactive list (pages that
are allocated but are most likely to be used for paging), and the Uni-
fied Buffer Cache (UBC) least recently used (LRU) list.
free
Total number of pages that are clean and available for use.
wire
Total number of pages that are currently in use and cannot be used for
paging (not a real list).
fault
Number of address translation faults that have occurred.
cow Number of copy-on-write page faults, which occur if the requested page
is shared by a parent process and one or more child processes (using
the fork function) and if one of the processes needs to modify the
page. In this case, VM loads a new address into the translation buffer
and copies the contents of the requested page into the new address for
modification by the process.
zero
Number of zero-filled-on-demand page faults, which occur if VM cannot
find the page in the internal data structures and if the requested page
is new and has never been referenced. In this case, VM initializes a
physical page (the contents of the page are zeroed out) and loads the
address into the page table.
react
Number of pages that have been faulted while on the inactive list.
pin Number of requests for pages from a pager.
pout
Number of pages that have been paged out.
Interrupt information:
in Number of nonclock device interrupts per second.
sy Number of system calls called per second.
cs Number of task and thread context switches per second.
CPU information:
us Percentage of user time for normal and priority processes.
sy Percentage of system time.
id Percentage of idle time.
Specify -f to display fork statistics only. Specify -s for a single
display of accumulated statistics, as well as page size.
SEE ALSO
Commands: iostat(1)
-------------- next part --------------
iostat(1) iostat(1)
NAME
iostat - Reports I/O statistics
SYNOPSIS
iostat [drive...] [interval] [count]
DESCRIPTION
The iostat command reports the following information:
+ For terminals (collectively), the number of characters read and writ-
ten per second.
+ For each disk, the number of transfers per second, bytes transferred
per second (in kilobytes), and the milliseconds per average seek. Not
all disk drives report seek times.
+ For the system, the percentage of time the system has spent in user
mode, in user mode running low priority (nice) processes, in system
mode, and idling.
To compute this information, iostat counts the number of seeks and data
transfer completions, the number of words transferred for each disk, and
the collective number of input and output characters for terminals. Also,
each sixtieth of a second, iostat examines the state of each disk and makes
a tally if the disk is active. From these numbers and given the transfer
rates of the devices, it is possible to determine the average seek times
for each device.
OPERANDS
drive...
Forces iostat to display specific drives. If drive is not specified,
iostat displays the first four drives (even if more than four disk
drives are configured in the system).
interval
Causes iostat to report once each interval seconds. The first report
is for all time since a reboot, and each subsequent report is for the
last interval only.
count
Specifies the number of reports. For example, iostat 1 10 would pro-
duce 10 reports at 1-second intervals. You cannot specify count
without interval because the first numeric argument to iostat is
assumed to be interval.
If a disk drive is attached and configured but has never been accessed,
iostat displays the disk name as dkn, where n is the drive number of
the console name for the drive. For example, if dka500 is the console
name of the never accessed disk, the name iostat uses is dk500.
EXAMPLES
The output from this example displays cpu, terminal, and disk statistics
for the first four disks on the system providing 5 reports in 1 second
intervals.
# iostat 1 5
tty rz1 rz2 rz3 rz4 cpu
tin tout bps tps bps tps bps tps bps tps us ni sy id
1 52 2 0 1 0 13 1 4 1 8 0 9 83
1 16 7 1 2 0 5 2 2 0 3 0 10 87
0 0 0 0 0 0 0 0 0 0 0 0 1 98
2 2 2 1 0 0 50 6 0 0 9 0 9 82
1 191 2 1 0 0 47 6 0 0 8 0 9 83
Note that this example does not show the average seek times (msps) for the
disk drives. Not all disk drives report seek time.
SEE ALSO
Commands: vmstat(1)
list Anton Burkhalter
Henrik,
I have no access to Tru64 4.x systems...
Here are some output examples from "uptime", I have implemented a simple
client script which reports the uptime to the hobbit server, every day I
had a blackout for 1 hour in de RRD. I have fixed it, the reason for
that was:
# date
Sun Aug 7 17:19:22 CEST 2005
# uptime
17:19 up 90 days, 56 mins, 1 user, load average: 0.00, 0.01, 0.00
# date
Sun Aug 7 17:23:58 CEST 2005
# uptime
17:24 up 90 days, 1 hr, 1 user, load average: 0.00, 0.00, 0.00
# date
Sun Aug 7 17:24:21 CEST 2005
# uptime
17:24 up 90 days, 1:01, 1 user, load average: 0.02, 0.02, 0.01
==> There are 13 parameters, if uptime is some days + 1..59 mins (or 1 hr).
==> For the next 23 hours we have just 12 parameters.
Here the output on Solaris 8:
$ uptime
5:30pm up 8 day(s), 16:42, 1 user, load average: 0.06, 0.02, 0.02
On Linux:
$ uptime
7:30pm up 8 days, 17:20, 1 user, load average: 0.00, 0.00, 0.00
And here some outputs from "vmstat -P" from Compaq Tru64 UNIX V5.1B
(Rev. 2650)
# vmstat -P
Total Physical Memory = 6144.00 M
= 786432 pages
Physical Memory Clusters:
start_pfn end_pfn type size_pages / size_bytes
0 885 pal 885 / 6.91M
885 786423 os 785538 / 6137.02M
786423 786432 pal 9 / 72.00k
Physical Memory Use:
start_pfn end_pfn type size_pages / size_bytes
885 1057 scavenge 172 / 1.34M
1057 2217 text 1160 / 9.06M
2217 2469 data 252 / 1.97M
2469 2963 bss 494 / 3.86M
2963 3257 kdebug 294 / 2.30M
3257 3264 cfgmgmt 7 / 56.00k
3264 3266 locks 2 / 16.00k
3266 3280 pmap 14 / 112.00k
3280 5374 unixtable 2094 / 16.36M
5374 5518 logs 144 / 1.12M
5518 23905 vmtables 18387 / 143.65M
23905 786423 managed 762518 / 5957.17M
============================
Total Physical Memory Use: 785538 / 6137.02M
Managed Pages Break Down:
free pages = 18273
active pages = 119391
inactive pages = 241854
wired pages = 82351
ubc pages = 300821
==================
Total = 762690
WIRED Pages Break Down:
vm wired pages = 11097
ubc wired pages = 0
meta data pages = 23494
malloc pages = 38790
contig pages = 3741
user ptepages = 3774
kernel ptepages = 789
free ptepages = 9
==================
Total = 81694
#
# vmstat -P
Total Physical Memory = 2048.00 M
= 262144 pages
Physical Memory Clusters:
start_pfn end_pfn type size_pages / size_bytes
0 396 pal 396 / 3.09M
396 262135 os 261739 / 2044.84M
262135 262144 pal 9 / 72.00k
Physical Memory Use:
start_pfn end_pfn type size_pages / size_bytes
396 545 scavenge 149 / 1.16M
545 1711 text 1166 / 9.11M
1711 1970 data 259 / 2.02M
1970 2464 bss 494 / 3.86M
2464 2757 kdebug 293 / 2.29M
2757 2764 cfgmgmt 7 / 56.00k
2764 2766 locks 2 / 16.00k
2766 2780 pmap 14 / 112.00k
2780 3979 unixtable 1199 / 9.37M
3979 4027 logs 48 / 384.00k
4027 10065 vmtables 6038 / 47.17M
10065 262135 managed 252070 / 1969.30M
============================
Total Physical Memory Use: 261739 / 2044.84M
Managed Pages Break Down:
free pages = 14634
active pages = 54190
inactive pages = 112275
wired pages = 48779
ubc pages = 22341
==================
Total = 252219
WIRED Pages Break Down:
vm wired pages = 9513
ubc wired pages = 0
meta data pages = 7780
malloc pages = 22728
contig pages = 3686
user ptepages = 4479
kernel ptepages = 272
free ptepages = 7
==================
Total = 48465
#
# vmstat -P
Total Physical Memory = 4096.00 M
= 524288 pages
Physical Memory Clusters:
start_pfn end_pfn type size_pages / size_bytes
0 397 pal 397 / 3.10M
397 524279 os 523882 / 4092.83M
524279 524288 pal 9 / 72.00k
Physical Memory Use:
start_pfn end_pfn type size_pages / size_bytes
397 545 scavenge 148 / 1.16M
545 1436 text 891 / 6.96M
1436 1612 data 176 / 1.38M
1612 1845 bss 233 / 1.82M
1845 2062 kdebug 217 / 1.70M
2062 2069 cfgmgmt 7 / 56.00k
2069 2071 locks 2 / 16.00k
2071 2085 pmap 14 / 112.00k
2085 3745 unixtable 1660 / 12.97M
3745 3841 logs 96 / 768.00k
3841 16012 vmtables 12171 / 95.09M
16012 524279 managed 508267 / 3970.84M
============================
Total Physical Memory Use: 523882 / 4092.83M
Managed Pages Break Down:
free pages = 159031
active pages = 94097
inactive pages = 186424
wired pages = 43159
ubc pages = 25704
==================
Total = 508415
WIRED Pages Break Down:
vm wired pages = 8260
ubc wired pages = 0
meta data pages = 15665
malloc pages = 10142
contig pages = 3750
user ptepages = 4808
kernel ptepages = 526
free ptepages = 8
==================
Total = 43159
#
Regards,
Tony
David Gore wrote: Unfortunately we are on Tru64 4.x
list Henrik Størner
Ok, thanks to David and Anton the Hobbit client should now support OSF/1 4.x and 5.x fully. The problem Anton reported with the format of the uptime output was already fixed in my code, since I had the same problem from a Linux box resulting in 1 hour where the load graph wasn't being updated. So I think Hobbit is in pretty good shape when it comes to support for various Unix systems. The client should work with AIX, FreeBSD, HP-UX, Linux, NetBSD, OpenBSD, OSF/1, Solaris and Darwin/Mac OS X. If anyone feels I've left out their favourite Unix platform, let me know - with a bit of help from You, I'm sure we can get it working. I've tested the *BSD, Linux and Solaris clients myself. Bob Gordon kindly helped with the Darwin support, which should be working now (except for the netstat data, will do that tomorrow). If someone could confirm that AIX, HP-UX and OSF/1 work (with whatever version of those you have), it would be nice. You'll need to use the latest snapshot of Hobbit from http://www.hswn.dk/beta/, and it's a good idea to make sure you use the latest client version if you've installed the 4.1.1 version. Regards, Henrik
list Al Jeffcoat
Hello Henrik, I know that you had said that you were not working on a windows client. What I don't recall is seeing anywhere if the BB clients will continue working with the new version of Hobbit, for platforms that are not on the list below. That's the only thing holding me from moving up to the new code. I'll probably update tomorrow anyway, and I'll confirm for you about the AIX platform when I get the chance. Thanks again for all your hard work. Al
▸
-----Original Message----- From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] Sent: Sunday, August 07, 2005 5:23 PM To: user-ae9b8668bcde@xymon.invalid Subject: [hobbit] Hobbit client OS support (was: OSF physical memory ..) Ok, thanks to David and Anton the Hobbit client should now support OSF/1 4.x and 5.x fully. The problem Anton reported with the format of the uptime output was already fixed in my code, since I had the same problem from a Linux box resulting in 1 hour where the load graph wasn't being updated. So I think Hobbit is in pretty good shape when it comes to support for various Unix systems. The client should work with AIX, FreeBSD, HP-UX, Linux, NetBSD, OpenBSD, OSF/1, Solaris and Darwin/Mac OS X. If anyone feels I've left out their favourite Unix platform, let me know - with a bit of help from You, I'm sure we can get it working. I've tested the *BSD, Linux and Solaris clients myself. Bob Gordon kindly helped with the Darwin support, which should be working now (except for the netstat data, will do that tomorrow). If someone could confirm that AIX, HP-UX and OSF/1 work (with whatever version of those you have), it would be nice. You'll need to use the latest snapshot of Hobbit from http://www.hswn.dk/beta/, and it's a good idea to make sure you use the latest client version if you've installed the 4.1.1 version. Regards, Henrik
This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any review, use, or distribution of this e-mail message and any attached files is strictly prohibited. This communication may contain material protected by Federal privacy regulations, attorney-client work product, or other privileges. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message. To reply to our email administrator directly, send an email to: user-ecde3bbc361d@xymon.invalid . If this e-mail message concerns a contract matter, be advised that no employee or agent is authorized to conclude any binding agreement on behalf of Orlando Regional Healthcare by e-mail without express written confirmation by an officer of the corporation. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Orlando Regional Healthcare.
list Henrik Størner
▸
On Sun, Aug 07, 2005 at 10:35:53PM -0400, Jeffcoat, Al wrote:
I know that you had said that you were not working on a windows client.
I'm not, but a friend of mine is looking into it. It's the only major platform that Hobbit doesn't support yet, so it is moving up on the priority list.
▸
What I don't recall is seeing anywhere if the BB clients will continue working with the new version of Hobbit, for platforms that are not on the list below.
The BB clients - Unix or Windows - will continue to work with Hobbit. No change there. Regards, Henrik
list Dirk Kastens
Hi,
▸
Henrik Stoerner schrieb:
(except for the netstat data, will do that tomorrow). If someone could confirm that AIX, HP-UX and OSF/1 work (with whatever version of those you have), it would be nice.
I just tried to compile the snapshot under AIX 5.1 ML08 using
gcc and gmake. The compilation stops with the following error:
In file included from /home/hobbit/snapshot/include/libbbgen.h:24,
from sendmsg.c:35:
/home/hobbit/snapshot/include/../lib/osdefs.h:21: conflicting types for `socklen_t'
/usr/include/sys/socket.h:80: previous declaration of `socklen_t'
sendmsg.c: In function `sendtobbd':
sendmsg.c:322: warning: passing arg 5 of `getsockopt' from incompatible pointer type
make[1]: *** [sendmsg.o] Error 1
make[1]: Leaving directory `/home/hobbit/snapshot/lib'
make: *** [lib-client] Error 2
Dirk
list Henrik Størner
▸
On Mon, Aug 08, 2005 at 03:21:24PM +0200, Dirk Kastens wrote:
I just tried to compile the snapshot under AIX 5.1 ML08 using
gcc and gmake. The compilation stops with the following error:
In file included from /home/hobbit/snapshot/include/libbbgen.h:24,
from sendmsg.c:35:
/home/hobbit/snapshot/include/../lib/osdefs.h:21: conflicting types for
`socklen_t'
/usr/include/sys/socket.h:80: previous declaration of `socklen_t'Could you send me the contents of the "include/config.h" file ? Also, please cut-and-paste this command and send me the output: gcc -c -o build/testfile.o build/test-socklent.c; echo $? Thanks, Henrik
list Dirk Kastens
Hi Henrik,
Could you send me the contents of the "include/config.h" file ?
Good news, the compilation succeeded. I had an old version of gcc installed when I did the first compilation. After the update I called "make clean", deleted the Makefile and called configure and make again, but the config.h hasn't been rebuild. I just deleted the file manually and now the compilation works. Best wishes, Dirk
list Michael Nemeth
OK with the latest snapshot 09-Aug-2005 Im able to compile on: Solaris 2.6 with no issues, hp11 with no issues except changing CC=cc to CC=gcc hp1020 issue: the -lnsl flag , library not found. I tried -lresolv no luck . I removed both and it compiled; is this OK does the client use this? At this time I cannot test if they actually work except for hpux 11. With hpux 11 client two issues: the network I/O graph stopped working . Stop working after a snapshot from last week. Looks like it worked with 4.1.1. I tried stopping hobbit and removing the rrd with no luck. Next is not a big issue yet (it may/should be on my Classed side where clearcase runs) Disk is picking automounts: /sw1/usr/local 4183116 4010394 172722 96% /usr/local this is an automount /home02/nemethm 4138510 3608164 530346 88% /home/nemethm this is an automount /dev/vg00/lvol4 19539 5144 14395 27% /home00 /dev/vg01/lvol2 4106336 2620740 1485596 64% /home01 /dev/vg01/lvol3 4138510 3608165 530345 88% /home02 / Also when I move to my classed side I have to be able to filter out my clearcase directoried: /home/vobs/dddd 4138510 3608165 530345 88% /vob/dddd the mounted on point should alway be /vob/ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | _p_ Mike Nemeth | ___| |_____ email(w) user-609d3fab5b2d@xymon.invalid Work: XXX XXX-XXXX |><___________) | Home Page:http://www.geocities.com/mjnemeth/ | Work Page:http://faraday.motown.lmco.com:3000/~nemethm/ | Work Page:http://ortsweb/~mnemeth/ |++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
list Henrik Størner
▸
On Tue, Aug 09, 2005 at 10:26:16AM -0400, Michael Nemeth wrote:
OK with the latest snapshot 09-Aug-2005 Im able to compile on: Solaris 2.6 with no issues, hp11 with no issues except changing CC=cc to CC=gcc
Great.
▸
hp1020 issue: the -lnsl flag , library not found. I tried -lresolv no luck . I removed both and it compiled; is this OK does the client use this?
If it compiles OK, then it isn't needed. All library dependencies are resolved at compile/link time.
▸
At this time I cannot test if they actually work except for hpux 11. With hpux 11 client two issues: the network I/O graph stopped working . Stop working after a snapshot from last week. Looks like it worked with 4.1.1. I tried stopping hobbit and removing the rrd with no luck.
Please send me a copy of the client/tmp/msg.txt from this client. I did some work on the netstat parser, so it is quite possible that I broke something - having a sample of the input data makes testing a lot easier.
▸
Next is not a big issue yet (it may/should be on my Classed side where clearcase runs) Disk is picking automounts: /sw1/usr/local 4183116 4010394 172722 96% /usr/local this is an automount
OK, I need your expertise here: As you can see in the hobbiclient-hpux.sh script, it runs the command "df -Pk" to get the df data. What options can be added to the df command line to avoid picking up these mounts ? Regards, Henrik
list Michael Nemeth
As far a df goes there are really no options to do this You can look for fs types but there are several valid ones. In BB I just grepped df -Pk | grep ^/dev Actual the two I listed are lofs ; automounted on the system itselt ,loopback . Ive attached client/tmp/msg.txt Aslo note Ive built a Sol 2.8 client with no problem .
▸
Henrik Stoerner wrote:
On Tue, Aug 09, 2005 at 10:26:16AM -0400, Michael Nemeth wrote:OK with the latest snapshot 09-Aug-2005 Im able to compile on: Solaris 2.6 with no issues, hp11 with no issues except changing CC=cc to CC=gccGreat.hp1020 issue: the -lnsl flag , library not found. I tried -lresolv no luck . I removed both and it compiled; is this OK does the client use this?If it compiles OK, then it isn't needed. All library dependencies are resolved at compile/link time.At this time I cannot test if they actually work except for hpux 11. With hpux 11 client two issues: the network I/O graph stopped working . Stop working after a snapshot from last week. Looks like it worked with 4.1.1. I tried stopping hobbit and removing the rrd with no luck.Please send me a copy of the client/tmp/msg.txt from this client. I did some work on the netstat parser, so it is quite possible that I broke something - having a sample of the input data makes testing a lot easier.Next is not a big issue yet (it may/should be on my Classed side where clearcase runs) Disk is picking automounts: /sw1/usr/local 4183116 4010394 172722 96% /usr/local this is an automountOK, I need your expertise here: As you can see in the hobbiclient-hpux.sh script, it runs the command "df -Pk" to get the df data. What options can be added to the df command line to avoid picking up these mounts ? Regards, Henrik
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | _p_ Mike Nemeth | ___| |_____ email(w) user-609d3fab5b2d@xymon.invalid Work: XXX XXX-XXXX |><___________) | Home Page:http://www.geocities.com/mjnemeth/ | Work Page:http://faraday.motown.lmco.com:3000/~nemethm/ | Work Page:http://ortsweb/~mnemeth/ |++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Attachments (1)
list Henrik Størner
▸
On Tue, Aug 09, 2005 at 02:31:21PM -0400, Michael Nemeth wrote:
As far a df goes there are really no options to do this You can look for fs types but there are several valid ones. In BB I just grepped df -Pk | grep ^/dev
Well, you can do that in the Hobbit client as well. The ~hobbit/client/bin/hobbitclient-hp-ux.sh client program *is* a shell script, so sticking your grep on the df command there will work. I'll look at your netstat output. Henrik
list Michael Nemeth
I Though I tried it before and it didn't work! So I tied it again and realized you're parsing for the header line! So I ended up with this: echo "[df]" echo "Filesystem 1024-blocks Used Available Capacity Mounted on" df -Pk | grep ^/dev Looks good now. Also this is the client on the hobbit server , ive been restarting the server to get client change but I assume its ok to use the runclient.sh script. One other thing , one other thing , a popular Distro of Perl for the hp goes in /opt/perl but others go in /usr and /usr/local and the old one in /usr/contrib. Ive all of them on system . The config script pick one I don't want to use; so Ive been edit the perl.sh just to have /opt/perl in it. Be nice if I could just supply this as an option the configure. BTW Thanks for the great support and great program!
▸
Henrik Stoerner wrote:
On Tue, Aug 09, 2005 at 02:31:21PM -0400, Michael Nemeth wrote:As far a df goes there are really no options to do this You can look for fs types but there are several valid ones. In BB I just grepped df -Pk | grep ^/devWell, you can do that in the Hobbit client as well. The ~hobbit/client/bin/hobbitclient-hp-ux.sh client program *is* a shell script, so sticking your grep on the df command there will work. I'll look at your netstat output. Henrik
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | _p_ Mike Nemeth | ___| |_____ email(w) user-609d3fab5b2d@xymon.invalid Work: XXX XXX-XXXX |><___________) | Home Page:http://www.geocities.com/mjnemeth/ | Work Page:http://faraday.motown.lmco.com:3000/~nemethm/ | Work Page:http://ortsweb/~mnemeth/ |++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
list Anton Burkhalter
Hi Henrik, This is just to complete the picture...
▸
Ok, thanks to David and Anton the Hobbit client should now support OSF/1 4.x and 5.x fully.
uptime on OSF/1 Tru64 5.1B on a system with an uptime less than 1 minute: # uptime 16:15 up 1 user, load average: 0.37, 0.26, 0.16 # # uptime 16:16 up 1 min, 1 user, load average: 0.70, 0.37, 0.24 Regards, Toni
list Henrik Størner
▸
On Thu, Aug 11, 2005 at 07:13:09AM -0400, Michael Nemeth wrote:
One other thing , one other thing , a popular Distro of Perl for the hp goes in /opt/perl but others go in /usr and /usr/local and the old one in /usr/contrib. Ive all of them on system . The config script pick one I don't want to use; so Ive been edit the perl.sh just to have /opt/perl in it. Be nice if I could just supply this as an option the configure.
The perl check is actually a left-over from the old perl-based maint.pl script. None of Hobbit requires Perl anymore. So I've just deleted that check from the configure script. Henrik