09-17-2007
Identifying and grouping OS processes and APP processes
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is it possible to have a main script (i will call it main.ksh) that executes say, 4 other scripts (sub_prog_1.ksh, sub_prog_2.ksh etc..) from within this main.ksh (simultaneously/in parallel), have them run in the background and communicate back to main.ksh when complete?
My guess is to use... (1 Reply)
Discussion started by: google
1 Replies
2. UNIX for Dummies Questions & Answers
What command string will locate ONLY the PID of a process and ouput only the number of PID of the process? (1 Reply)
Discussion started by: mma_buc_98
1 Replies
3. Shell Programming and Scripting
does anyone know how to lower the sheduling priority of a process. (3 Replies)
Discussion started by: master_6ez
3 Replies
4. Filesystems, Disks and Memory
write a program create two processes to run a for loop which adds numbers 1 to n , say one process adds odd numbers and other adds even numbers (1 Reply)
Discussion started by: jayaram_miryabb
1 Replies
5. UNIX for Dummies Questions & Answers
Can someone tell how to find out how long a process has been running? I want to find something that is usually there that the paging system can check on.
Thanks (4 Replies)
Discussion started by: Beetlejuice
4 Replies
6. UNIX for Advanced & Expert Users
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
Discussion started by: ukndoit
4 Replies
7. UNIX for Dummies Questions & Answers
how to identify the processes running by giving the parent process id (1 Reply)
Discussion started by: trichyselva
1 Replies
8. UNIX for Dummies Questions & Answers
Hi all,
I needed a little help. It's OS thing.
Suppose I have 2 machine connect over a network, I will call my machines as M1and M2.
If I copy a files from M1 to M2. What tasks are these two machine performing for copy to work.
My assumption is that M1 is performing read action and... (1 Reply)
Discussion started by: vishwesh
1 Replies
9. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
10. Windows & DOS: Issues & Discussions
I have a .NET application that remotely starts, stops, and gets status of Windows services and scheduled tasks. I would like to add the capability of starting, stopping, and getting status of remote AIX applications also. Based on some preliminary research, one option may be to use 3rd party .NET... (0 Replies)
Discussion started by: auser1
0 Replies
RENICE(8) System Manager's Manual RENICE(8)
NAME
renice - alter priority of running processes
SYNOPSIS
renice priority [ [ -p ] pid ... ] [ [ -g ] pgrp ... ] [ [ -u ] user ... ]
DESCRIPTION
Renice alters the scheduling priority of one or more running processes. The who parameters are interpreted as process ID's, process group
ID's, or user names. Renice'ing a process group causes all processes in the process group to have their scheduling priority altered.
Renice'ing a user causes all processes owned by the user to have their scheduling priority altered. By default, the processes to be
affected are specified by their process ID's. To force who parameters to be interpreted as process group ID's, a -g may be specified. To
force the who parameters to be interpreted as user names, a -u may be given. Supplying -p will reset who interpretation to be (the
default) process ID's. For example,
renice +1 987 -u daemon root -p 32
would change the priority of process ID's 987 and 32, and all processes owned by users daemon and root.
Users other than the super-user may only alter the priority of processes they own, and can only monotonically increase their ``nice value''
within the range 0 to PRIO_MAX (20). (This prevents overriding administrative fiats.) The super-user may alter the priority of any
process and set the priority to any value in the range PRIO_MIN (-20) to PRIO_MAX. Useful priorities are: 20 (the affected processes will
run only when nothing else in the system wants to), 0 (the ``base'' scheduling priority), anything negative (to make things go very fast).
FILES
/etc/passwd to map user names to user ID's
SEE ALSO
getpriority(2), setpriority(2)
BUGS
Non super-users can not increase scheduling priorities of their own processes, even if they were the ones that decreased the priorities in
the first place.
4th Berkeley Distribution November 17, 1996 RENICE(8)