I should not use the word "IDLE" then. Normally, our online reports have 30 min time out. However, if the user closed/exit our online report menu improperly, then the process will still running for days even weeks. When more and more of this kind of processes running, our system will slow down.
If I run "ps auxw | grep webrepn", I get this:
Look at under %CPU, 10% for each one, it really will slow down the system.
So two things I need here, 1) to find out the pid of those process, 2) kill them.
Any thoughts?
Last edited by Franklin52; 03-26-2013 at 04:03 AM..
Reason: Please use code tags for data and code samples
Hi,
Please let us know of any possiblity of identifying and killing unix proces invoked externally (by an external tool which does not create a session). 'who' command gives idle time of sessions. But what we are looking for is idle time of a process. 'ps' command gives the elapsed/running... (1 Reply)
My max user parm is set to 1050. I'm currently at 1038 this is causing major slow downs on the server. I looking for a way log off "idle" user logins with out having to do it individually. :confused: (5 Replies)
Hi,
In my network we uses the NetTerm program to connect us to HP-UX 10.x server from windows workstations, but in some cases the user doesn't logout and close it by window's x button. The problem is that in HP-UX the user and all his tasks remain active and when he enter again HP-UX creates a... (12 Replies)
Dear Friends ,
I am using DB2 database in AIX 5.3 server . In my server some IDLE process are generated after several times which I need to kill it manually each and every time .
The process I query like following :
root@bagpuss $ ps auxw|sort -r +3|head -10
USER PID %CPU %MEM ... (3 Replies)
Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it
This is how we execute the script (and this is the requirement) ... (2 Replies)
Hi All,I have a problem with my kill idle script.my script is supposed to kill the user sessions which are idle for more than 2 hours.But is is killing the sessions which are idle for less than 2 hrs also.I dont know the exact time after which the script is killing,but it is less than 2 hours i am... (3 Replies)
What I need to learn is how to use a script that launches background processes, and then kills those processes as needed.
The script successfully launches the script. But how do I check to see if the job exists before I kill it?
I know my problem is mostly failure to understand parameter... (4 Replies)
Hi Team ,
I have one process named as cec_analysiseool that is running on unix box machine now i want to kill this process so please advise what will be the ideal command to kill this , what i have tried is :confused:
kill -9 `ps -ef | grep cec_analysiseool | grep -v grep | awk '{print $2}'` (2 Replies)
Discussion started by: unclesamm
2 Replies
LEARN ABOUT MOJAVE
dtruss
dtruss(1m) USER COMMANDS dtruss(1m)NAME
dtruss - process syscall details. Uses DTrace.
SYNOPSIS
dtruss [-acdeflhoLs] [-t syscall] { -p PID | -n name | command }
DESCRIPTION
dtruss prints details on process system calls. It is like a DTrace version of truss, and has been designed to be less intrusive than truss.
Of particular interest is the elapsed times and on cpu times, which can identify both system calls that are slow to complete, and those
which are consuming CPU cycles.
Since this uses DTrace, only users with root privileges can run this command.
OPTIONS -a print all details
-b bufsize
dynamic variable buffer size. Increase this if you notice dynamic variable drop errors. The default is "4m" for 4 megabytes per CPU.
-c print system call counts
-d print relative timestamps, us
-e print elapsed times, us
-f follow children as they are forked
-l force printing of pid/lwpid per line
-L don't print pid/lwpid per line
-n name
examine processes with this name
-W name
wait for a process matching this name
-o print on-cpu times, us
-s print stack backtraces
-p PID examine this PID
-t syscall
examine this syscall only
EXAMPLES
run and examine the "df -h" command
# dtruss df -h
examine PID 1871
# dtruss -p 1871
examine all processes called "tar"
# dtruss -n tar
run test.sh and follow children
# dtruss -f test.sh
run the "date" command and print elapsed and on cpu times,
# dtruss -eo date
FIELDS
PID/LWPID
Process ID / Lightweight Process ID
RELATIVE
relative timestamps to the start of the thread, us (microseconds)
ELAPSD elapsed time for this system call, us
CPU on-cpu time for this system call, us
SYSCALL(args)
system call name, with arguments (some may be evaluated)
DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
bose descriptions explaining the output.
EXIT
dtruss will run forever until Ctrl-C is hit, or if a command was executed dtruss will finish when the command ends.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO procsystime(1M), dtrace(1M), truss(1)version 0.80 Jun 17, 2005 dtruss(1m)