Sponsored Content
Top Forums UNIX for Advanced & Expert Users How to know whether my perodic thread is working fine Post 302252513 by MarkSeger on Wednesday 29th of October 2008 04:51:09 PM
Old 10-29-2008
collectl - http://collectl.sourceforge.net/

collectl has the ability to monitor threads in either top more or rolling output. if these are short-lived, you can always set a monitoring interval to < 1 sec! In fact, if you know the process name and issue the following command:

collectl --top --procfile cxxx --protopt t -i:0.01

it will look for all processes with the string xxx anywhere in their command line as well as any threads with that name once every 0.01 seconds!

-mark
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

NAWK Script not working fine

Hello to all can any one help me out with a nawk script. Actually i am having a shell script which uses nawk pattern searching and it is not parsing the file properly. I have been debugging it since long time, but nt able 2 find the root cause.. If any one can help me out with this one .. (3 Replies)
Discussion started by: dheeraj19584
3 Replies

2. Solaris

GUI not working... CLI is working fine

Hello, I have X4500 running Solaris 10. I can access it through CLI but I cannot see the GUI. When I reboot it, the GUI works till all the files are loaded (ie., the initial boot sequence) and it prompts me to enter username and password and there it ends. The screen just has a blinking cursor... (4 Replies)
Discussion started by: bharu_sri
4 Replies

3. Solaris

Thread Dump not working

Hello, I'm running a kill -QUIT on few process IDs (OS: Solaris) but the Thread Dump is empty. Can you please help me get it back on? Since I'm quite new to this, I'm not aware of the checks. Please let me know for the info required to debug this issue. Thanks! (3 Replies)
Discussion started by: DevendraG
3 Replies

4. Programming

Thread Not Working

Hy, In my current knowledge, i write the code for multiply 3x3 matrix to it self . . . Problem is that pthread_create function is not working. Here is my code :wall::wall::wall::wall: Please help me to this problem ! Thanks (4 Replies)
Discussion started by: UsmanUrRehman
4 Replies

5. Shell Programming and Scripting

Getting issue while running it from cron while manually working fine

Hello, I am working one one script where I am using the below code which is using to connect with MKS client when I run my script manually it works effiecently i.e. it connects with MKS client but when I run it from CRON it doesn't connect. 1)Can some one tell when it is running from cron... (1 Reply)
Discussion started by: anuragpgtgerman
1 Replies

6. Shell Programming and Scripting

Sed script not working properly on Solaris (works fine on AIX)?

Hi, I have a problem with a SED script that works fine on AIX but does not work properly on a Solaris system. The ksh script executes the SED and puts the output in HTML in tables. But the layout of the output in HTML is not shown correctly(no tables, no color). Can anyone tell if there is... (7 Replies)
Discussion started by: Faith111
7 Replies

7. Shell Programming and Scripting

Script not working in cron but working fine manually

Help. My script is working fine when executed manually but the cron seems not to catch up the command when registered. The script is as follow: #!/bin/sh for file in file_1.txt file_2.txt file_3.txt do awk '{ print "0" }' $file > tmp.tmp mv tmp.tmp $file done And the cron... (2 Replies)
Discussion started by: jasperux
2 Replies

8. Shell Programming and Scripting

Getting Command not found error Even though Script is working fine

Hi friends, I am using below script to do some work. But even though script is working fine but while executing it i am getting command not found error. :( Here is the script :- #!/bin/sh Names="name.txt" ###main##### for LINE in `cat ${Names}` do ... (3 Replies)
Discussion started by: harpal singh
3 Replies

9. Shell Programming and Scripting

sed command not working inside ksh script but works fine outside

Hi, I am a bit confused ,why would a sed command work fine outside of ksh script but not inside. e.g I want to replace all the characters which end with a value and have space at end of it. so my command for it is : sed -i "s/$SEPARATOR /$SEPARATOR/g" file_name This is working fine in... (8 Replies)
Discussion started by: vital_parsley
8 Replies
PMCOLLECTL(1)						      General Commands Manual						     PMCOLLECTL(1)

NAME
pmcollectl - collect data that describes the current system status SYNOPSIS
pmcollectl [-f file | -p file ...] [options ...] DESCRIPTION
pmcollectl is a system-level performance monitoring utility that records or displays specific operating system data for one or more sets of subsystems. Any of the subsystems (such as CPU, Disks, Memory or Sockets) can be included or excluded from data collection. Data can either be displayed immediately to a terminal, or stored in files for retrospective analysis. pmcollectl is a python(1) script providing much of the functionality available from the collectl(1) Linux utility (which happens to be written in perl(1)). It makes use of the Performance Co-Pilot (PCP) toolkit to simplify its implementation, as well as provide more of the collectl functional- ity on platforms other than Linux. pmcollectl has two primary modes of operation: 1. Record Mode (-f or --filename option) which reads data from a live system and writes output to a file or displays it on a terminal. 2. Playback Mode (-p or --playback option) which reads data from one or more PCP archive files and displays output on a terminal. Note that these files are not raw collectl format data, rather they are archives created by the pmlogger(1) utility (possibly indirectly, through use of the -f option to pmcollectl). RECORD MODE OPTIONS
In this mode data is taken from a live system and either displayed on the terminal or written to a PCP archive. -h host Display metrics from host instead of displaying metrics from the local host. -c, --count samples The number of samples to record. -f, --filename filename This is the name of a PCP archive to write the output to. -i, --interval interval This is the sampling interval in seconds. The default is 1 second. -R, --runtime duration Specify the duration of data collection where the duration is a number followed by one of wdhms, indicating how many weeks, days, hours, minutes or seconds the collection is to be taken for. PLAYBACK MODE OPTIONS
In this mode, data is read from one or more PCP data files that were generated with the recording option, or indirectly via the pmlogger utility. -f, --filename filename If specified, this is the name of a PCP archive to write the output to (rather than the terminal). -p, --playback filename Read data from the specified PCP archive files(s). COMMON OPTIONS
The following options are supported in both record and playback modes. --help Display standard help message. -s, --subsys subsystem This field controls which subsystem data is to be collected or played back for. The rules for displaying results vary depending on the type of data to be displayed. If you write data for CPUs and DISKs to a raw file and play it back with -sc, you will only see CPU data. If you play it back with -scm you will still only see CPU data since memory data was not collected. To see the current set of default subsystems, which are a subset of this full list, use -h. The default is "cdn", which stands for CPU, Disk and Network summary data. SUMMARY SUBSYSTEMS c - CPU d - Disk f - NFS V3 Data j - Interrupts m - Memory n - Networks y - Slabs (system object caches) DETAIL SUBSYSTEMS This is the set of detail data from which in most cases the corresponding summary data is derived. So, if one has 3 disks and chooses -sd, one will only see a single total taken across all 3 disks. If one chooses -sD, individual disk totals will be reported but no totals. C - CPU D - Disk F - NFS Data J - Interrupts M - Memory node data, which is also known as NUMA data N - Networks Y - Slabs (system object caches) Z - Processes --verbose Display output in verbose mode. This often displays more data than in the default mode. When displaying detail data, verbose mode is forced. Furthermore, if summary data for a single subsystem is to be displayed in verbose mode, the headers are only repeated occasionally whereas if multiple subsystems are involved each needs their own header. SEE ALSO
PCPIntro(1), collectl(1), perl(1), python(1), pmlogger(1), pmcd(1), pmprobe(1), pmval(1), PMAPI(3), and pcp.conf(5). Performance Co-Pilot PCP PMCOLLECTL(1)
All times are GMT -4. The time now is 10:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy