05-29-2009
nmon
All of a suden it happened.
10 More Discussions You Might Find Interesting
1. AIX
good morning
what is the better solution to examen a P570 ?
because i use topas and nmon, and the results are totally different !!!
with nmon, i have 80% free cpu, and with nmon, i have 90% of used cpu !!!!!!
i take a shot with an intervall of 10s during 10 mn.
thank you (0 Replies)
Discussion started by: pascalbout
0 Replies
2. AIX
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)
Discussion started by: johnf
3 Replies
3. AIX
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)
Discussion started by: habuzahra
3 Replies
4. AIX
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)
Discussion started by: jegtoro
3 Replies
5. AIX
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)
Discussion started by: vjm
6 Replies
6. AIX
HI,
I have downloaded nmon 3.3c nmon analyzer, and run the command on aix ./nmon -f
After that I have terminated the process and found .nmon file.
when i have tried to open that file in nmon analyzer i.e in excel I am getting the error "no valid input data nmon run may have failed"
... (8 Replies)
Discussion started by: manoj.solaris
8 Replies
7. Red Hat
Hi guys,
as per subject i am setting up NMON for the above OS but it is 64-bit Linux.
I downloaded the 32-bit NMON for RHEL45 as it is the only one available for RHEL45.
However, I ran into problem with the binary file.
# ./nmon_x86_rhel45
./nmon_x86_rhel45: error while loading shared... (13 Replies)
Discussion started by: DrivesMeCrazy
13 Replies
8. AIX
Hi guys, I am an Oracle DBA and I have an account with some databases on an AIX 5.3 server. I am trying to figure out if I really need to add memory to this box or not, the account team keeps pushing me to make a decision and I don't want to waste their money if I don't need to right now, we could... (4 Replies)
Discussion started by: nibbsbitt
4 Replies
9. Shell Programming and Scripting
Hi, my name is Steve Ngai from Malaysia. This is my first post. Hope to learn more about Unix from this forum.
My first question is can nmon be customized? When I run nmon, I need to manually type c to see CPU usage, then m for memory usage. Can I pass it some nmon option to automatically see... (2 Replies)
Discussion started by: ngaisteve1
2 Replies
10. AIX
Hi all,
I am currently having trouble to get nmon to print me the actual CPU usage for an interval for a process.
According to the manual, something like
# time nmon -t -C cron -s 5 -c 2 -F outfile
real 0m0.98s
user 0m0.03s
sys 0m0.04s
should print out at least the process... (15 Replies)
Discussion started by: zaxxon
15 Replies
LEARN ABOUT MOJAVE
git-cherry
GIT-CHERRY(1) Git Manual GIT-CHERRY(1)
NAME
git-cherry - Find commits yet to be applied to upstream
SYNOPSIS
git cherry [-v] [<upstream> [<head> [<limit>]]]
DESCRIPTION
Determine whether there are commits in <head>..<upstream> that are equivalent to those in the range <limit>..<head>.
The equivalence test is based on the diff, after removing whitespace and line numbers. git-cherry therefore detects when commits have been
"copied" by means of git-cherry-pick(1), git-am(1) or git-rebase(1).
Outputs the SHA1 of every commit in <limit>..<head>, prefixed with - for commits that have an equivalent in <upstream>, and + for commits
that do not.
OPTIONS
-v
Show the commit subjects next to the SHA1s.
<upstream>
Upstream branch to search for equivalent commits. Defaults to the upstream branch of HEAD.
<head>
Working branch; defaults to HEAD.
<limit>
Do not report commits up to (and including) limit.
EXAMPLES
Patch workflows
git-cherry is frequently used in patch-based workflows (see gitworkflows(7)) to determine if a series of patches has been applied by the
upstream maintainer. In such a workflow you might create and send a topic branch like this:
$ git checkout -b topic origin/master
# work and create some commits
$ git format-patch origin/master
$ git send-email ... 00*
Later, you can see whether your changes have been applied by saying (still on topic):
$ git fetch # update your notion of origin/master
$ git cherry -v
Concrete example
In a situation where topic consisted of three commits, and the maintainer applied two of them, the situation might look like:
$ git log --graph --oneline --decorate --boundary origin/master...topic
* 7654321 (origin/master) upstream tip commit
[... snip some other commits ...]
* cccc111 cherry-pick of C
* aaaa111 cherry-pick of A
[... snip a lot more that has happened ...]
| * cccc000 (topic) commit C
| * bbbb000 commit B
| * aaaa000 commit A
|/
o 1234567 branch point
In such cases, git-cherry shows a concise summary of what has yet to be applied:
$ git cherry origin/master topic
- cccc000... commit C
+ bbbb000... commit B
- aaaa000... commit A
Here, we see that the commits A and C (marked with -) can be dropped from your topic branch when you rebase it on top of origin/master,
while the commit B (marked with +) still needs to be kept so that it will be sent to be applied to origin/master.
Using a limit
The optional <limit> is useful in cases where your topic is based on other work that is not in upstream. Expanding on the previous example,
this might look like:
$ git log --graph --oneline --decorate --boundary origin/master...topic
* 7654321 (origin/master) upstream tip commit
[... snip some other commits ...]
* cccc111 cherry-pick of C
* aaaa111 cherry-pick of A
[... snip a lot more that has happened ...]
| * cccc000 (topic) commit C
| * bbbb000 commit B
| * aaaa000 commit A
| * 0000fff (base) unpublished stuff F
[... snip ...]
| * 0000aaa unpublished stuff A
|/
o 1234567 merge-base between upstream and topic
By specifying base as the limit, you can avoid listing commits between base and topic:
$ git cherry origin/master topic base
- cccc000... commit C
+ bbbb000... commit B
- aaaa000... commit A
SEE ALSO
git-patch-id(1)
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-CHERRY(1)