Sponsored Content
Full Discussion: System Activity Report
Special Forums UNIX and Linux Applications Infrastructure Monitoring System Activity Report Post 302891370 by Perderabo on Wednesday 5th of March 2014 10:24:38 AM
Old 03-05-2014
Ummm, 1,000,000,000 is a lot of seconds.

60 * 60 * 24 = 86,400 seconds per day.
86,400 * 365 = 31,536,000 seconds per year
so it's
315,536,000 seconds per decade

1,000,000,000 seconds is over 31 years. You should reboot your systems at least once a decade anyway.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

mksysb and system activity

Hello, With AIX 5.3 is it possible to run a mksysb with users logged into the system? The users are accessing a database app that runs on a separate physical disk than the system files. Does this even matter? Thanks (1 Reply)
Discussion started by: samsa1mi
1 Replies

2. AIX

System activity

Hi, I want to find program's file read,write for a particular time.For example i am executing an application called test1, this will get input from some parameter files(file1,file2,file3) and it will write to some files(file4,file5), so i want to execute one program which will capture these... (3 Replies)
Discussion started by: gnanadurai_it
3 Replies

3. Shell Programming and Scripting

How to monitor system activity while executing tests

I need to monitor system activity (RAM, CPU usage, execution time) while running some tests on solaris, linux and aix and save the output. Please advise whether there's a utility available for these systems? How can time the execution of the command? Thanks! (2 Replies)
Discussion started by: smovla
2 Replies

4. UNIX for Dummies Questions & Answers

Strange system activity no matter what I try

When I choose to encrypt my drive during a Linux install, it encryps it, but I receive errors in dmesg and in ~/.xsessions-errors during use. The first error is in dmesg where it sometimes shows errors writing to the encypted device. The second error is in ~/.xsessions-errors with an error about... (0 Replies)
Discussion started by: justgoogleit
0 Replies

5. Red Hat

system activity and information data

Hi all, i need to collect all system activities data(processes running, disk details, memory, etc), system logs and things related. i heard of cfg2html but its not available for my CentOS distro(i may need to install separately but thats not what i wana do). i can use sar for syatem... (1 Reply)
Discussion started by: ajayyadavmca
1 Replies

6. Red Hat

RHEL Linux process activity monitoring tool from windows 7 system

I have 2 RHEL 5.9 system where customized applications are running. These 2 servers are with in a network (LAN) with each other.One application in say Server 1 can talk to another application in server 2 and vice versa. The applications are exchanging data among each other. Recently I am... (0 Replies)
Discussion started by: Anjan Ganguly
0 Replies
IOPING(1)							   User Commands							 IOPING(1)

NAME
ioping - simple disk I/O latency monitoring tool SYNOPSYS
ioping [-LCDRq] [-c count] [-w deadline] [-p period] [-i interval] [-s size] [-S wsize] [-o offset] device|file|directory ioping -h | -v DESCRIPTION
This tool lets you monitor I/O latency in real time. OPTIONS
-c count Stop after count requests. -w deadline Stop after deadline time passed. -p period Print raw statistics for every period requests. -i interval Set time between requests to interval (1s). -s size Request size (4k). -S size Working set size (1m). -o offset Offset in input file. -L Use sequential operations rather than random. This also sets request size to 256k (as in -s 256k). -C Use cached I/O. -D Use direct I/O. -R Disk seek rate test (same as -q -i 0 -w 3 -S 64m). -q Suppress human-readable output. -h Display help message and exit. -v Display version and exit. Argument suffixes For options that expect time argument (-i and -w), default is seconds, unless you specify one of the following suffixes (case-insensitive): us, usec microseconds ms, msec milliseconds s, sec seconds m, min minutes h, hour hours For options that expect "size" argument (-s, -S and -o), default is bytes, unless you specify one of the following suffixes (case-insensi- tive): s disk sectors (a sector is always 512). k, kb kilobytes p memory pages (a page is always 4K). m, mb megabytes g, gb gigabytes t, tb terabytes For options that expect "number" argument (-p and -c) you can optionally specify one of the following suffixes (case-insensitive): k kilo (thousands, 1 000) m mega (millions, 1 000 000) g giga (billions, 1 000 000 000) t tera (trillions, 1 000 000 000 000) EXIT STATUS
Returns 0 upon success. The following error codes are defined: 1 Invalid usage (error in arguments). 2 Error during preparation stage. 3 Error during runtime. EXAMPLES
ioping . Show disk I/O latency using the default values and the current directory, until interrupted. ioping -c 10 -s 1M /tmp Measure latency on /tmp using 10 requests of 1 megabyte each. ioping -R /dev/sda Measure disk seek rate. ioping -RL /dev/sda Measure disk sequential speed. SEE ALSO
Homepage <http://code.google.com/p/ioping/>. AUTHORS
This program was written by Konstantin Khlebnikov <koct9i@gmail.com>. Man-page was written by Kir Kolyshkin <kir@openvz.org>. July 2011 IOPING(1)
All times are GMT -4. The time now is 01:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy