07-27-2006
Syed
Thanks RTM
IT is Tru64 unix
And we found the error why it is stopping after 2 hours
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have MATLAB INSTALLED IN MY SUN MACHINE >>
WHENEVER I USE IT THE CPU USAGE SHOWS ABT 90%
Seeing the vmstat shows that system calls and context switch counters reach a very high value .
What are these counters ( Man pages do not give much info on that) ....
The only thing i can make out that... (1 Reply)
Discussion started by: DPAI
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
In the unix command, "vmstat" we get information on Page memory.
what does the "mf" - "minor fault" is?
Regards,
Anent (3 Replies)
Discussion started by: anent
3 Replies
3. UNIX for Dummies Questions & Answers
When I exeute vmstat (e.g. vmstat 30 2),
in some machines I get some wierd result as the first line.
like: -117% or 208% for CPU idle percentage.
But the second line is alright.
Could someone explain this please.
Thanks !
Chaadana (4 Replies)
Discussion started by: chaandana
4 Replies
4. UNIX for Advanced & Expert Users
Hi,
what does mean the free colomne in out put of vmstat ? is it free espace of physical memory or of swap space on hard disk ?
Thank you (4 Replies)
Discussion started by: big123456
4 Replies
5. Solaris
This is something nowbody around me can explain:
vmstat (-S 5) shows a huge number of PI but when I try to monitor it in parallel with iostat - there is no IO activity to be seen that would correspond to this.
I have 16G RAM and 32G swap file.
I'll really appreciate if somebody can explain it.... (9 Replies)
Discussion started by: dkvent
9 Replies
6. Linux
Hi everyone,
I need to see some VM manager performance/behavior information on some Linux boxes regarding pages scanned/activation of the paging algorithm in order to get an idea if a given server needs more memory and is actually paging. In Aix servers, by using the vmstat cmd you... (1 Reply)
Discussion started by: jcpetela
1 Replies
7. Shell Programming and Scripting
Hi
I need to write a script to display VMSTAT every 5 seconds and I just need the memory columns - swap free re and just the numbers and the headers arent required.
For example
bash-3.00$ vmstat 5| awk '{print $4" "$5" "$6}'
disk faults cpu ------ This header isnt required
swap... (3 Replies)
Discussion started by: kapilk
3 Replies
8. AIX
I need some guidance on the differences in observations, not sure how significantly different are they.
Also, It would be nice to hear on the values and what the obvious tuning for performance missing.
Observation 1
ending vmstat -v 3948544 memory pages
ending vmstat -v ... (1 Reply)
Discussion started by: Snipper
1 Replies
9. Solaris
I'm trying to parse vmstat output with this:
vmstat | nawk '/0/{printf "%s\ \n", $5}'
but output is different on two sparc Solaris 10 servers, one is missing line with 'free'.
why ? (3 Replies)
Discussion started by: orange47
3 Replies
10. Linux
I m checking idle time using vmstat, below are the results
var=$(ssh wmtmgr@$hostname vmstat | tail -1 | awk '{print $15}')
89
and now im subtracting 89 with 100 & im getting expected results
expr 100 - $var
11
Now How can I get the result 11 in one line code? (4 Replies)
Discussion started by: sam@sam
4 Replies
LEARN ABOUT SUSE
stopping
stopping(7) Miscellaneous Information Manual stopping(7)
NAME
stopping - event signalling that a job is stopping
SYNOPSIS
stopping JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
DESCRIPTION
The stopping event is generated by the Upstart init(8) daemon when an instance of a job begins stopping. The JOB environment variable con-
tains the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs.
If the job is stopping normally, the RESULT environment variable will be ok, otherwise if the job is stopping because it has failed it will
be failed.
When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start,
main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job is stopping because it hit the respawn
limit.
Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either
EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received.
The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see
init(5) for more information.
If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not
found). See the system logs for the error.
init(8) will wait for all services started by this event to be running, all tasks started by this event to have finished and all jobs
stopped by this event to be stopped before allowing the job to continue stopping.
This allows jobs to depend on other jobs, safely stopping themselves before their dependency goes away. This event is typically combined
with the started(7) event by services.
Job configuration files may use the export stanza to export environment variables from their own environment into the stopping event. See
init(5) for more details.
EXAMPLE
A service that wishes to depend on another service might use:
start on started apache
stop on stopping apache
A task that must be run before another task or service is stopped might use:
start on stopping postgresql RESULT=ok
SEE ALSO
starting(7) started(7) stopped(7) init(5)
Upstart 2009-07-09 stopping(7)