a valid once off nmon command would be
where -s is the interval between runs and -c the number of times you want to run it. I assume you have interrupted your run before it had been finished so your data is corrupted ?
Kind regards
zxmaus
Thanks for your quick response, basically my requirement is to collect the NMON data for one day or 2 day,
so i have run the command ./nmon so that i can terminate in between if I want.
please let me know the version which i am using is correct or any other version i have to use
also let me know i have terminated the ./nmon process after 15 mins this time interval is sufficient?
Wheather i have to copy the file before terminating?
Anyone ever experienced a core dump when running NMON. I am running AIX 5.3 on an 8 CPU LPAR (P570). This has only recently started to happen. (3 Replies)
Can any one help where i can find articals about nomn
I need to know how to read this tools
┌─CPU-Utilisation-Small-View───────────────────────────────────────────────────┐
│ 0----------25-----------50----------75----------100│
│CPU User% Sys% Wait% Idle%| ... (3 Replies)
HI Im new on this world.
Im working with nmon and I understand that this tool generates a files that later with excel I can see the graphcial of my server.
The problem is that this process is execute manualy and I need to meake automatic.
How can I do That.
Sorry for my english!! :o (3 Replies)
Hi All,
I have a p550 server with 4 proc. But when i run nmon analyzer in cpu_sum it show 5 processors cpu0 cpu1 cpu2 cpu3 cpu4. Why it is showing 5 processors. (6 Replies)
I use NMON (Nigels Monitoring) in AIX. It creates a daily nmon log with the naming conventions of:
hostname_YYMMDD_0000.nmon
or
myserver_080902_0000.nmon
What I am interested in doing is creating a script that is executed on the first of each month to clean up last months *nmon files. .... (4 Replies)
We have processes that run on our AIX box that sometimes run away and end up consuming 99% of the CPU. I'd like to create a script that would attempt to monitor when this happens and send an email alert with the PID and CPU %. Has anyone done such a thing? I know that you can run the nmon output to... (6 Replies)
Hi All,
First of all, I am a DBA and not an AIX admin. I am new at using this NMON tool.
In interactive mode, I can start nmon, push 't' to have the list of process with their statistic (ie cpu% etc.).
I would like to know if there is a way to redirect that screen output into a log... (1 Reply)
Hello,
How can I know if ORACLE Database is running slow due to Memory or due to processing power ?
I have only Oracle Database running on a P4 with 4GB RAM.
Could anyone suggest any tools which can help me determine exactly if it is memory issue or processor issue. (43 Replies)
Discussion started by: filosophizer
43 Replies
LEARN ABOUT DEBIAN
io::async::timer::periodic
IO::Async::Timer::Periodic(3pm) User Contributed Perl Documentation IO::Async::Timer::Periodic(3pm)NAME
"IO::Async::Timer::Periodic" - event callback at regular intervals
SYNOPSIS
use IO::Async::Timer::Periodic;
use IO::Async::Loop;
my $loop = IO::Async::Loop->new;
my $timer = IO::Async::Timer::Periodic->new(
interval => 60,
on_tick => sub {
print "You've had a minute
";
},
);
$timer->start;
$loop->add( $timer );
$loop->run;
DESCRIPTION
This subclass of IO::Async::Timer implements repeating events at regular clock intervals. The timing may or may not be subject to how long
it takes the callback to execute. Iterations may be rescheduled runs at fixed regular intervals beginning at the time the timer was
started, or by a fixed delay after the previous code has finished executing.
For a "Timer" object that only runs a callback once, after a given delay, see instead IO::Async::Timer::Countdown. A Countdown timer can
also be used to create repeating events that fire at a fixed delay after the previous event has finished processing. See als the examples
in "IO::Async::Timer::Countdown".
EVENTS
The following events are invoked, either using subclass methods or CODE references in parameters:
on_tick
Invoked on each interval of the timer.
PARAMETERS
The following named parameters may be passed to "new" or "configure":
on_tick => CODE
CODE reference for the "on_tick" event.
interval => NUM
The interval in seconds between invocations of the callback or method. Cannot be changed if the timer is running.
first_interval => NUM
Optional. If defined, the interval in seconds after calling the "start" method before the first invocation of the callback or
method. Thereafter, the regular "interval" will be used. If not supplied, the first interval will be the same as the others.
Even if this value is zero, the first invocation will be made asynchronously, by the containing "Loop" object, and not
synchronously by the "start" method itself.
reschedule => STRING
Optional. Must be one of "hard", "skip" or "drift". Defines the algorithm used to reschedule the next invocation.
"hard" schedules each iteration at the fixed interval from the previous iteration's schedule time, ensuring a regular repeating
event.
"skip" schedules similarly to "hard", but skips over times that have already passed. This matters if the duration is particularly
short and there's a possibility that times may be missed, or if the entire process is stopped and resumed by "SIGSTOP" or similar.
"drift" schedules each iteration at the fixed interval from the time that the previous iteration's event handler returns. This
allows it to slowly drift over time and become desynchronised with other events of the same interval or multiples/fractions of it.
Once constructed, the timer object will need to be added to the "Loop" before it will work. It will also need to be started by the "start"
method.
AUTHOR
Paul Evans <leonerd@leonerd.org.uk>
perl v5.14.2 2012-10-24 IO::Async::Timer::Periodic(3pm)