09-06-2013
@anil510
Post the output of ps -eo pid,pcpu,pmem,user,args,etime,cmd --sort=start_time
This way we need not guess what you see.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Ok, so I know there's a way to do this, but I've been trying to find out all afternoon with no luck. I think it should print out something like this:
1 bin
2 daemon
6 duo
Where the numbers on the left are the number of processes being run by the user whose name is listed on the right. Is... (4 Replies)
Discussion started by: Duo11
4 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Can any one help me on this.
How to capture the running process for two hours with an interval of 10 sec.
Thanks in andvance
Double post, continued here, thread closed (0 Replies)
Discussion started by: sarathkumar
0 Replies
3. Shell Programming and Scripting
Hi,
Can any one help me on this.
How to capture the running process for two hours with an interval of 10 sec.
Thanks in andvance (1 Reply)
Discussion started by: sarathkumar
1 Replies
4. Shell Programming and Scripting
Hi,
How can i capture the running process for 2 hours.
Thanks in advance.:b: (1 Reply)
Discussion started by: sarathkumar
1 Replies
5. Shell Programming and Scripting
Hi Experts,
Please help me in this.
I am trying this code on AIX 5.3.
I need list of jobs that executed in last 4 hours.
I have a schedule on this script - cron executes it and sends mail to me for every 2 hours.
I have a Job time and have around 100 jobs those execute daily.
What all i need... (2 Replies)
Discussion started by: rajubollas
2 Replies
6. UNIX for Dummies Questions & Answers
Is there a way to find out the total no of processes that were running ?
- 2 or 3 hours before
- list those no of processes (3 Replies)
Discussion started by: jansat
3 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
new to the forum and new to Unix but I have an issue which is annoying on a new level. I have included a short and full version for anyone needing more information.
Short Version
I am running a set of scripts that work and run fine. one of the scripts arranges the first... (4 Replies)
Discussion started by: Delboy4000
4 Replies
8. Shell Programming and Scripting
I have unix epoch time 1441678454803, Can you please help me to print this time in below format ?
DAY,HOUR,MIN,SEC
Appreciate your help!!!
Thanks,
Prince (7 Replies)
Discussion started by: prince1987
7 Replies
9. UNIX for Beginners Questions & Answers
Hi,
Is it possible to display processes which have been running for more than a 5hrs using a variation of the ps -ef command?
Regards,
Manny (5 Replies)
Discussion started by: mantas44
5 Replies
10. UNIX for Beginners Questions & Answers
HI
can someone help me to check the process running more than 2 hours.
I have the below command which shows the time and process id, however, I only need the processes running more than 2 hours. (8 Replies)
Discussion started by: Vinod
8 Replies
trace(1) General Commands Manual trace(1)
Name
trace - trace system calls of programs
Syntax
trace [options] cmd args...
Description
The command with no flag arguments traces for the given cmd and args all system calls made and prints a time stamp, the PID, call and/or
return values and arguments and puts its output in the file trace.dump.
Options
-f filename
Puts dump in file filename.
-z Echos arguments only.
Only one of the following option arguments can be specified at one time.
-c# Traces given PIDs and their children. Up to sixteen PIDs can be specified.
-g# Traces given groups only. Up to sixteen Group IDs can be specified.
-p# Traces given PIDs only. Up to sixteen PIDs can be specified.
-s# Traces given system calls only. Up to sixteen PIDs can be specified.
-u# Traces given UIDs only. Up to sixteen PIDs can be specified.
Examples
trace -f ls.dump ls -l /dev >ls.out
runs the cmd ls -l /dev and puts the trace in ls.dump and output in ls.out.
trace -f csh.trace -p $$ &
will trace your login shell in the background. To stop the trace just send it a termination signal (that is, kill -TERM trace_pid).
Restrictions
Due to security, no one, not even the super-user can trace anyone else's programs. This sort of negates some of the usefulness of the -g
and -u flags.
The program cannot be traced.
Only 16 numbers can be given to the -c, -p, -g, -u, and -s flags.
The kernel configuration file must contain the following:
options SYS_TRACE
pseudo-device sys_trace
In addition, the superuser must use the following command sequence to create the device:
cd /dev
MAKEDEV trace
If both lines are not in the configuration file or if the device is not made, the message "Cannot open /dev/trace" appears.
Files
/dev/trace read only character special device for reading syscall data.
trace.dump default file for the system call trace data.
See Also
open(2), close(2), ioctl(2), select(2), read(2), trace(5)
trace(1)