09-20-2012
There is no trace command which works on processes that don't exist.
Check tomcat's log files instead.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
In my organization in order for anyone to go to any Unix server they have to go through "SERVER A" and login as themselves.
Then people are free to go enywhere they please.
For example:
SERVER A, loggs in as himself
telnets to SERVER B, loggs in as guest
telnets to SERVER C, loggs in as... (8 Replies)
Discussion started by: jraitsev
8 Replies
2. Shell Programming and Scripting
Does anyone know if there is a util out there to run through a shell script and be able to trace the function call tree. I have inherited some code and the original author was ****mad**** keen on functions - even ones called only once!
If anyone knows of anything I would appreciate it - web... (3 Replies)
Discussion started by: ajcannon
3 Replies
3. Linux
Hi all,
Under top command you could see some iowait output.
Is any way to locate which process(s) is causing the high percentage of iowait?
17:48:39 up 19 days, 18:54, 3 users, load average: 3.24, 3.14, 3.17
392 processes: 389 sleeping, 1 running, 2 zombie, 0 stopped
CPU states: cpu user... (3 Replies)
Discussion started by: will_mike
3 Replies
4. AIX
Hi,
Sometimes when I want to unmount some filesystem I get "The requested resource is busy." error.
In such a case I try to find and kill process that uses that filesystem. I do that on random.
Is there a right way to find whitch prosesses use filesystem resource at given time ?
thanks... (1 Reply)
Discussion started by: vilius
1 Replies
5. Shell Programming and Scripting
Hi
I am working in ksh and getting the trace after trying to remove the file which in some cases does not exist:
$ my_script
loadfirm.dta.master: No such file or directory
The code inside the script which produces this trace is the following:
] || rm ${FILE}.master >> /dev/null
for... (3 Replies)
Discussion started by: aoussenko
3 Replies
6. Solaris
Hi all,
We have a server having much processes running. It is very difficuilt to trace the exact consuming more memory. Howerver, it shows CPU usage in sequence but how memory?
Tried working with TOP command.
Please let me know if something not clear.
Thanks,
Deepak (5 Replies)
Discussion started by: naw_deepak
5 Replies
7. UNIX for Advanced & Expert Users
Hello,
I execute an application on my Unix AIX Server and that one crashes after reading some files. These files are very big (80 Mbytes), the application is a CVS Repository.
I have found with a comparaison on a Solaris Server that there are system limitations on my AIX Server in the... (2 Replies)
Discussion started by: steiner
2 Replies
8. AIX
I don't know when the process will start and end, I need write a script to trace it's cpu/memory usage when it is runing. How to write this script? (2 Replies)
Discussion started by: rainbow_bean
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
i want to track a process using its PID in SOLARIS.
i have a code in C++ , which memory is increasing steeply increasing every 20 days, from the code i couldn't see any memory leak.
is there any way in UNIX where with the help of PID i can trace the Process usage evry hour.
... (3 Replies)
Discussion started by: senkerth
3 Replies
10. UNIX for Beginners Questions & Answers
I will initiate a process from Server1 and the flow is as follow
Server1 --> Web server --> Application server --> DB Server
Note all seperate unix servers.
Now I need to put a trace for that process to track the timings from each server.
Like the below trace should be there:
... (5 Replies)
Discussion started by: saraperu
5 Replies
LEARN ABOUT FREEBSD
trace
KTRACE(1) BSD General Commands Manual KTRACE(1)
NAME
ktrace -- enable kernel process tracing
SYNOPSIS
ktrace [-aCcdi] [-f trfile] [-g pgrp | -p pid] [-t trstr]
ktrace [-adi] [-f trfile] [-t trstr] command
DESCRIPTION
The ktrace utility enables kernel trace logging for the specified processes. Kernel trace data is logged to the file ktrace.out. The kernel
operations that are traced include system calls, namei translations, signal processing, and I/O.
Once tracing is enabled on a process, trace data will be logged until either the process exits or the trace point is cleared. A traced
process can generate enormous amounts of log data quickly; It is strongly suggested that users memorize how to disable tracing before
attempting to trace a process. The following command is sufficient to disable tracing on all user-owned processes, and, if executed by root,
all processes:
$ ktrace -C
The trace file is not human readable; use kdump(1) to decode it.
The utility may be used only with a kernel that has been built with the ``KTRACE'' option in the kernel configuration file.
The options are:
-a Append to the trace file instead of recreating it.
-C Disable tracing on all user-owned processes, and, if executed by root, all processes in the system.
-c Clear the specified trace points associated with the given file or processes.
-d Descendants; perform the operation for all current children of the designated processes.
-f trfile
Log trace records to trfile instead of ktrace.out.
-g pgid
Enable (disable) tracing on all processes in the process group (only one -g flag is permitted).
-i Inherit; pass the trace flags to all future children of the designated processes.
-p pid Enable (disable) tracing on the indicated process id (only one -p flag is permitted).
-t trstr
Specify the list of trace points to enable or disable, one per letter. If an explicit list is not specified, the default set of
trace points is used.
The following trace points are supported:
c trace system calls
f trace page faults
i trace I/O
n trace namei translations
p trace capability check failures
s trace signal processing
t trace various structures
u userland traces
w context switches
y trace sysctl(3) requests
+ trace the default set of trace points - c, i, n, p, s, t, u, y
command
Execute command with the specified trace flags.
The -p, -g, and command options are mutually exclusive.
EXAMPLES
# trace all kernel operations of process id 34
$ ktrace -p 34
# trace all kernel operations of processes in process group 15 and # pass the trace flags to all current and future children
$ ktrace -idg 15
# disable all tracing of process 65
$ ktrace -cp 65
# disable tracing signals on process 70 and all current children
$ ktrace -t s -cdp 70
# enable tracing of I/O on process 67
$ ktrace -ti -p 67
# run the command "w", tracing only system calls
$ ktrace -tc w
# disable all tracing to the file "tracedata"
$ ktrace -c -f tracedata
# disable tracing of all user-owned processes
$ ktrace -C
SEE ALSO
kdump(1)
HISTORY
The ktrace command appeared in 4.4BSD.
BUGS
Only works if trfile is a regular file.
BSD
August 26, 2014 BSD