01-25-2007
Indeed, you do not boot Unix systems unless there is a valid reason to do so.
Unix isn't Windows which messes up memory etc. all the time.
And booting a system just to kill processes isn't a very good reason. Processes should terminate in a "normal" way. If they don't you better talk to the developer and kill them manually when ever the need occurs.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I'd like to know if to reboot a work station I need the root permission.
If not what is the procedure ( commands or steps ) to reboot a work station.
Cheers
Mohsen (5 Replies)
Discussion started by: mohsen
5 Replies
2. UNIX for Dummies Questions & Answers
Any recommended book on Unix & Shell Programming (7 Replies)
Discussion started by: endeavour1985
7 Replies
3. UNIX for Dummies Questions & Answers
Hello I was wondering if anyone had a Unix book recommendation. Just one book, that can give me a good foundation in Unix and has plenty of hands on exercises to follow along with on my Unix terminal? Thank you (1 Reply)
Discussion started by: vedder191
1 Replies
4. UNIX for Dummies Questions & Answers
hello,
I want to learn more on unix, and being use to windows (VERY SAD i know) i want to learn more, but which unix is recommended for a new user to become novice to advance? also what is a great website to look into to gain more knowledge of unix, i have the commands pretty good in my head,... (0 Replies)
Discussion started by: Siten0308
0 Replies
5. AIX
Hello all,
I am working on an AIX 5.3L machine. I am currently trying to work on getting all of my Tuxedo servers booted for my app. However, some of these servers also use the Oracle 10g R2 client to connect to the 10g2 DB. AT FIRST, everything was working fine.
Anyway, one night all... (3 Replies)
Discussion started by: swvahokie
3 Replies
6. UNIX for Advanced & Expert Users
Hi,
please could someone advise the best command to shutdown and then for it to reboot back online again.
Note: I shall be doing this from a telent session.
regards
venhart (3 Replies)
Discussion started by: venhart
3 Replies
7. Solaris
I have to execute 2 commands everytime i reboot my Solaris machine.
Simple "share" and "chown" commands.
Is there anywhere (maybe a config file or something) where I can include these commands so that I do not have to manually run them everytime I reboot the machine?
Any help appreciated... (2 Replies)
Discussion started by: lydiaEd
2 Replies
8. Shell Programming and Scripting
We have number of servers which belongs to platforms Solaris, AIX,HP-UX and LINUX. Monitoring tool 'Patrol Agent' process run on the servers to check for the server health and communicate with the Patrol server through the port 5181. During scheduled reboot and maintenance of servers we do receive... (1 Reply)
Discussion started by: subharai
1 Replies
9. UNIX for Dummies Questions & Answers
My knowledge is weak in understanding NIS servers, setting up user accounts, mounting network file systems, clearing stale NFS handles, those sorts of things that I encounter but my IT server team handles.
Can anyone recommend a good book on the subject? Something to demystify mount points,... (1 Reply)
Discussion started by: srhadden
1 Replies
10. Solaris
Hi all,
My remote unix machine failed unexpectly, and I am unable to login to it.
Here is what I can see on the screen -
> Boot device: .... File and args: -i
> Boot load failed.
> The file just loaded does not appear to be executable.
> {1} ok
How can I fix this problem? Has... (1 Reply)
Discussion started by: bhakti.gandhi
1 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)