10-02-2008
Foreground them or kill them.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hi All
my Redhat Linux server stopped responding to pings all together. and am also not able to ping out of the box. There are however no issues with internet connectivity and my application is working fine. When I tried to ping another machine (Win98) i could see the pings coming from my... (2 Replies)
Discussion started by: skotapal
2 Replies
2. UNIX for Dummies Questions & Answers
One of my linux machines has a 'stopped' process which i need to find. How do i find the process that is iin 'stopped' mode. I am running red hat linux enterprise.
Frank
I have now answered this myself with the following command:
ps -e j |grep Z (2 Replies)
Discussion started by: frankkahle
2 Replies
3. 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
4. Linux
Hi All,
I am user of a Linux machine and I have approximatly 15 cronjobs scheduled in my crontab. Yesterday my administrator made LDAP active on my userid and all the things are doing fine after that. But all cronjobs for my user id stored in my crontab have stopped working after that.
Could... (1 Reply)
Discussion started by: bisla.yogender
1 Replies
5. Solaris
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. (2 Replies)
Discussion started by: wilsonee
2 Replies
6. Shell Programming and Scripting
Hello people,
I had these cronjobs scheduled in some Unix boxes which were running fine until yesterday.But then the password was changed for that user id and then the jobs stopped working. As far as i know cron jobs run from super user. I am completely lost over here now.
Thanks. (2 Replies)
Discussion started by: King Nothing
2 Replies
7. UNIX for Advanced & Expert Users
UNIX Tutorial Five
% kill %jobnumber
Does that not work on a stopped process? I've tried to kill a stopped process and it is not working. Or do you need a certain type of shell for this to work? I don't see anything about this in my man pages. (3 Replies)
Discussion started by: cokedude
3 Replies
8. Shell Programming and Scripting
Hi,
I've been wondering about this for a while and I just don't know where to start looking. Some of my scripts always get stopped when I start them with
$ script.plx &in the shell (bash, on Debian lenny, logged in via ssh from a Mac OS machine using Terminal.app). After a few seconds I keep... (4 Replies)
Discussion started by: mregine
4 Replies
9. Shell Programming and Scripting
Hello Team,
In my shell script, it stopped without killing it.
Could you please help why ?
Below is the code :
get_dpi44_currentFiles()
{
truncate --size 0 $dpi_44_fixed_currentFileList
if ssh $dpi_srvr_44 -p 2222 "ls $dpi_44_sourceFilesDir/fixed | grep '\.tgz$'" >... (5 Replies)
Discussion started by: sadique.manzar
5 Replies
waitid(2) System Calls Manual waitid(2)
NAME
waitid - wait for child process to change state
SYNOPSIS
DESCRIPTION
The function suspends the calling process until one of its children changes state. It records the current state of a child in the structure
pointed to by infop. If a child process changed state prior to the call to returns immediately.
The idtype and id arguments are used to specify which children will wait for.
If idtype is will wait for the child with a process ID equal to (pid_t)pid.
If idtypeis will wait for any child with a process group ID equal to (pid_t)pid.
If idtypeis will wait for any children and id is ignored.
The options argument is used to specify which state changes will wait for. It is formed by OR-ing together one or more of the following
flags:
Wait for processes that have exited.
Status will be returned for any child that has stopped upon receipt
of a signal.
Status will be returned for any child that was stopped and has been
continued.
Return immediately if there are no children to wait for.
Keep the process whose status is returned in
infop in a waitable state. This will not affect the state of the process; the process may be waited for
again after this call completes.
The infop argument must point to a structure. If returns because a child process was found that satisfied the conditions indicated by the
arguments idtype and options, then the structure pointed to by infop will be filled in by the system with the status of the process. The
si_signo member will always be equal to
RETURN VALUE
If returns due to the change of state of one of its children, 0 is returned. Otherwise, -1 is returned and is set to indicate the error.
ERRORS
The function will fail if:
[ECHILD] The calling process has no existing unwaited-for child processes.
[EINTR] The function was interrupted due to the receipt of a signal by the calling process.
[EINVAL] An invalid value was specified for options, or idtype and id specify an invalid set of processes.
APPLICATION USAGE
Threads Considerations
In a multi-threaded application, only the calling thread is suspended by
will not return until all threads in the process have reached the desired state. For example, if the or options are specified, will not
return until all threads in the process have terminated, stopped or continued respectively.
SEE ALSO
exec(2), exit(2), wait(2), <sys/wait.h>.
CHANGE HISTORY
First released in Issue 4, Version 2.
waitid(2)