how to know which processes are created by running a job?
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 730
- Joined: Tue Nov 04, 2008 10:14 am
- Location: Bangalore
how to know which processes are created by running a job?
Hi,
If I run a job it will create processes which will run on the operating system, how to know the name and PID of these processes.
I am running the job using dsjob command.
If I run a job it will create processes which will run on the operating system, how to know the name and PID of these processes.
I am running the job using dsjob command.
-
- Participant
- Posts: 2
- Joined: Fri Mar 06, 2009 12:22 am
- Location: India
Re: how to know which processes are created by running a job
ps -ef| grep "userID" is the easiest and best UNIX to know about the status of running jobs...
newmoonera
(Enjoy the Beauty of Life)
(Enjoy the Beauty of Life)
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Re: how to know which processes are created by running a job
Code: Select all
ps -ef| grep "userID"
Code: Select all
ps -ef | grep Job1
Code: Select all
ps -ef|grep DSD
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.![Wink :wink:](./images/smilies/icon_wink.gif)
Genius may have its limitations, but stupidity is not thus handicapped.
![Wink :wink:](./images/smilies/icon_wink.gif)
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Yes, that is correct. If you are trying to catch this at run time then it is very difficult. Show PIDs is good but you need to get this along with the process list to do anything useful. The phantom process will be the parent of most of these processes. I tried to pull together these processes to total all their sizes. We had an issue of running out of RAM. So we wanted to know how big each job was as far as how much RAM it used. The idea was to run just enough jobs not to swap or page.
The conductor starts section leaders which run sections of jobs these have the job name in their command line. So you need to find the processes which have the job names in their command line. Then trace back its parent to find the section leaders. One job can fire up hundreds of processes. If you trace up to a parent and then back down then you can get all the processes but you cannot trace back to process 1 which is the kernel.
Good luck. I got tired and gave up. I got real close. It is a pretty hairy shell script though.
The conductor starts section leaders which run sections of jobs these have the job name in their command line. So you need to find the processes which have the job names in their command line. Then trace back its parent to find the section leaders. One job can fire up hundreds of processes. If you trace up to a parent and then back down then you can get all the processes but you cannot trace back to process 1 which is the kernel.
Good luck. I got tired and gave up. I got real close. It is a pretty hairy shell script though.
Mamu Kim