04-18-2009
If your process is running on foreground Ctrl + C can kill existing process.
Or use ps -ef | grep "Script Name".
then use kill -9 "Process ID".
Or you can use ps -ef | more to find all process IDs and then kill them one by one.
10 More Discussions You Might Find Interesting
1. Solaris
Well, I am not even sure if its failing, cause at the other end I have a select call and it wakes up and reads the data I sent fine.
Ok here is the issue, I have a UDP socket(non blocking) through which I push some data to another port. At the other end I have select loop, waiting for this data.... (6 Replies)
Discussion started by: Naanu
6 Replies
2. Solaris
Hi everybody,
I have an Unix box running Solaris and every day for 1 hour or 2 the box is stuck and I can only get this error message when trying to type a command :
bash-3.00$ vmstat 5
bash: fork: Resource temporarily unavailable
How can I trace what's is going wrong with this box ?... (5 Replies)
Discussion started by: unclefab
5 Replies
3. Solaris
installed 64bit 16GB VM on 64bit ESX server.
Written small C code to map the 2GB of memory by mmap after creating 3 child
and map getting failed by throwing "resource unavailable temporarily" after mapping 1.6 GB of memory out of 2GB. But same 1.5Gb memory mapping works fine.
I checked... (0 Replies)
Discussion started by: siddharoodh
0 Replies
4. UNIX for Dummies Questions & Answers
Hi,
Now I am programming to communicate with some network printer through TCP Socket program.By sending command "\033E 1\r" to printer,causes, check the port for error normally.
In my case i used following code
bytesSent = send( sockfd, "\033E 1\r",sizeof("\033E 1\r"), 0);
... (1 Reply)
Discussion started by: kavinsivakumar
1 Replies
5. Red Hat
First post, sorry to be a bother but this one has been dogging me. I have a process user (java application server) that trips a resource limit every couple weeks and need help finding what limit we're hitting.
First, this is what's running:
This is the error when jobs are run or the... (0 Replies)
Discussion started by: Katahdin
0 Replies
6. UNIX for Advanced & Expert Users
Solaris 10 Server refuse to connect :wall:
fork: Resource temporarily unavailable , server unexpectedly unavailable network connection , refuse error, disconnect message, fatal error type2, (protocol error type2)
Issue has been resolved after taken few steps :b:
First of all need to check... (1 Reply)
Discussion started by: taherahmed
1 Replies
7. UNIX for Dummies Questions & Answers
I wrote a script that works most of the time but gave me
fork: resource temporarily unavailable
some of the time. I restarted my computer and now it runs fine but googling "fork: resource temporarily unavailable" and looking on the forums has not actually helped me figure out what exactly I... (3 Replies)
Discussion started by: monstrousturtle
3 Replies
8. Programming
Hello,
I am using the termios library to write data that I get from a Bluetooth device to a modem via serial.
The data arrive from the Bluetooth device correctly every 50ms and I have to bypass them on the serial ttyUSB3 where it is connected to a modem connected to a socket with static IP.
The... (10 Replies)
Discussion started by: enaud
10 Replies
9. UNIX for Dummies Questions & Answers
I wrote a perl program that simultaneously reads in data from 691 tar.gz files using zcat. I can run one instance of the program without any issues and the memory and swap sizes are negligible. However, when I attempt to run more than 1 I start to get fork: resource unavailable messages. Are... (6 Replies)
Discussion started by: aquinom85
6 Replies
10. Shell Programming and Scripting
Hi friends,
Working on a linux X86-64 bit system, I suddenly started getting this error (mentioned in subject) from various scripts.
I googled, found that there are couple of reason which causes this issue.
- less memory
I am pretty sure, memory seems to be stable on my system and at the... (15 Replies)
Discussion started by: clx
15 Replies
kill(1) General Commands Manual kill(1)
Name
kill - send a signal to a process
Syntax
kill [-sig] processid...
kill -l
Description
The command sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first
argument, that signal is sent instead of terminate. For further information, see
The terminate signal kills 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 (that is, processes resulting from the current login) are
signaled. This works only if you use and not if you use To kill a process it must either belong to you or you must be superuser.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using It
allows job specifiers ``%...'' so process ID's are not as often used as arguments. See for details.
Options
-l Lists signal names. The signal names are listed by `kill -l', and are as given in /usr/include/signal.h, stripped of the common SIG
prefix.
See Also
csh(1), ps(1), kill(2), sigvec(2)
kill(1)