Sponsored Content
Full Discussion: stopped processes
Top Forums UNIX for Dummies Questions & Answers stopped processes Post 302242518 by era on Thursday 2nd of October 2008 05:42:11 AM
Old 10-02-2008
Foreground them or kill them.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Server stopped pinging (in and out)

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

how to find which process is stopped

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

Monitoring Processes - Killing hung processes

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

Cronjobs stopped working

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

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. (2 Replies)
Discussion started by: wilsonee
2 Replies

6. Shell Programming and Scripting

cronjobs stopped working

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

Killing A Stopped Process

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

Scripts stopped in the shell

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

While true loop stopped

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
KILL(1) 						      General Commands Manual							   KILL(1)

NAME
kill - terminate a process with extreme prejudice SYNOPSIS
kill [ -sig ] processid ... kill -l DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu- ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in /usr/include/signal.h, stripped of the common SIG prefix. The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special meanings; see kill(2) for details. The killed processes must belong to the current user unless he is the super-user. The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1). Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill arguments. See csh(1) for details. SEE ALSO
csh(1), ps(1), kill(2), sigvec(2) BUGS
A replacement for ``kill 0'' for csh(1) users should be provided. 4th Berkeley Distribution April 20, 1986 KILL(1)
All times are GMT -4. The time now is 06:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy