12-10-2009
Kill, child, orphan, zombie and the likes are there since the seventies and are unlikely to disappear in the Unix context. They are actually pretty good metaphors while perhaps not "politically correct". Your proposal reminds me how many Unix people were upset when directories started to be referred as folders. Gratuitous changes are usually not welcome.
The first example is interesting as kill, both as a system call and a command, is a partly a misnomer. Kill is sending a signal to a process that effectively kill that process or not depending on settings. Its most frequent use is to kill so the name still seems adequate to me.
"stop" won't do as it is an existing special case which imply the process is resumable. "remove" might also be confusing as it is so commonly associated with unlinking a file.
You might want to post your aliases and start a poll about them ...
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Need a lot of help, need to find information on unix and how to use it, Has anybody ues the learnkey videos on unix teaching. (5 Replies)
Discussion started by: winter
5 Replies
2. UNIX for Dummies Questions & Answers
To anyone who asks which Unix is the best... or which one I should use...
Probably the best timeline I have ever seen.
Read this link... http://www.levenez.com/unix/history.html#08 (0 Replies)
Discussion started by: Kelam_Magnus
0 Replies
3. UNIX for Dummies Questions & Answers
am a windows Prof .... i deside to go with the UNIX .... but how can i start ......plz help me ........ (1 Reply)
Discussion started by: ekarak
1 Replies
4. UNIX for Dummies Questions & Answers
Hi
I have recently joined a bank as a tester. Initially I will be working on some test scripts and then I will be testing their data warehouse using SQL and Unix. I do have a very basic knowledge and understanding of both unix and sql. I am not sure how I will be using Unix to test their ... (2 Replies)
Discussion started by: kartikkumar84@g
2 Replies
5. Shell Programming and Scripting
Need to automate the following steps (OS--> AIX )
1. cd /advx/R8.1MR2/TOP/logs ( I navigate to this directory)
2. Monitor the current date ULOG for specific error pattern
=> ls -lrt ULOG.08*
-rw-rw-rw- 1 vssrt vssgrp 24370 Aug 01 23:57 ULOG.080112
-rw-rw-rw- 1 vssrt vssgrp ... (6 Replies)
Discussion started by: krchakr
6 Replies
6. What is on Your Mind?
This is an excellent video comment on modern society and the remix is good too:
https://www.youtube.com/watch?v=5DU1B_XkyIk
5DU1B_XkyIk
Watch the video above and post your comments. (3 Replies)
Discussion started by: Neo
3 Replies
7. What is on Your Mind?
Nice UNIX history article by John Loeffler, February, 05th 2019
UNIX: Building The Most Important OS in the World
The most widely used operating system in the world was a project born out of failure. (0 Replies)
Discussion started by: Neo
0 Replies
8. What is on Your Mind?
UNIX.com Hello World HUD YT Video
https://youtu.be/cs3dbPnzDV4
Check it out!
Subscribe, Like, Share, Comment .
Cyber Dystopia (Ep. 2) - The Myth of the Singularity Coming Soon! (3 Replies)
Discussion started by: Neo
3 Replies
KILL(2) System Calls Manual KILL(2)
NAME
kill - send signal to a process
SYNOPSIS
kill(pid, sig)
int pid, sig;
DESCRIPTION
Kill sends the signal sig to a process, specified by the process number pid. Sig may be one of the signals specified in sigvec(2), or it
may be 0, in which case error checking is performed but no signal is actually sent. This can be used to check the validity of pid.
The sending and receiving processes must have the same effective user ID, otherwise this call is restricted to the super-user. A single
exception is the signal SIGCONT, which may always be sent to any descendant of the current process.
If the process number is 0, the signal is sent to all processes in the sender's process group; this is a variant of killpg(2).
If the process number is -1 and the user is the super-user, the signal is broadcast universally except to system processes and the process
sending the signal. If the process number is -1 and the user is not the super-user, the signal is broadcast universally to all processes
with the same uid as the user except the process sending the signal. No error is returned if any process could be signaled.
For compatibility with System V, if the process number is negative but not -1, the signal is sent to all processes whose process group ID
is equal to the absolute value of the process number. This is a variant of killpg(2).
Processes may send signals to themselves.
RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
Kill will fail and no signal will be sent if any of the following occur:
[EINVAL] Sig is not a valid signal number.
[ESRCH] No process can be found corresponding to that specified by pid.
[ESRCH] The process id was given as 0 but the sending process does not have a process group.
[EPERM] The sending process is not the super-user and its effective user id does not match the effective user-id of the receiving
process. When signaling a process group, this error was returned if any members of the group could not be signaled.
SEE ALSO
getpid(2), getpgrp(2), killpg(2), sigvec(2)
4th Berkeley Distribution May 14, 1986 KILL(2)