AIXThis forum is for the discussion of IBM AIX.
eserver and other IBM related questions are also on topic.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
should collect a full days worth of information at 10 second slices. But when I kick this off it immediately stops. Now, it could be, and probably is, that I'm doing something wrong here. But, even using the example provided in the help (nmon64 -h) I get the same behavior.
Remember that the nmon collected data should have less than typycallly 300. This means that your collection interval should be about 5 minutes, and not 10 seconds if y ou want to use the collected data.
The following command line works for me, it's in a script I start with nohup :
nmon32 -F ../logs/myfile.nmon -r mytest-s30 -c400
You see that I use nmon32 because I have a 32 bits toy for playing today, but this syntax should also work with nmon64 on your system.
It seems real weird, the way this works. Contrary to the way most other scripts and programs work when they run. When I kick it off it, somehow, magically backgrounds itelf, possibly spawns some child processes, and the parent process disappears. Yet, the file that I tell it to write to still gets written to. An hour later, I've got an hours worth of data.
You know what ? I'm happy !
We do have a working script.
I wa very tired when I wrote this script, so I dropped almost anything in it.
We don't really know why, but it works.
So, let's use it, and let's wait until we happen to learn why it works.