12-11-2009
Oh, my goodness! The GOod PEople(tm) are on the loose!
Well, if we want to rename "kill" to "stop" why not rename "yes" to "just_say_no" or "tar" to a lightweight "feather"? How about renaming "cat" to something less ridiculuos to our other four-legged friends. With respect to our canine friends there should be a "dog" along with the "cat", yes? Not to mention some cozy (and probably rapidly-spawning) "rabbit" process, a "guinea-pig" and some cuddly "teddybear".
Not to forget the rude "du", which could be called "please_i_beg_your_pardon_but_isn't_this_obvious_already" and "shutdown" could be named "actively_seeking_chapter_eleven_protection_while_setting_free_some_workers_in_a_socially_acceptable _way" - hey, its even a lot easier to type that way, no?
How about signals? Hey, there is one called - horribile dictu - ABORT. Shouldn't this be called "CHOICE" from now on - or, better yet, be removed from the system in favour of a "LIFE" signal, which duplicates the process against the will of the system administrator? After all, as Jesus has no qualms with people killing people once they are grown up but detests people removing amorphous cell heaps he sure prefers system crashes over the stopping of processes not allowed to do all their intended purposes.
And, finally, how about renaming UNIX to "PC" (procreatively challenged)?
bakunin
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
LEARN ABOUT PHP
systemd.kill
SYSTEMD.KILL(5) systemd.kill SYSTEMD.KILL(5)
NAME
systemd.kill - Process killing procedure configuration
SYNOPSIS
service.service, socket.socket, mount.mount, swap.swap, scope.scope
DESCRIPTION
Unit configuration files for services, sockets, mount points, swap devices and scopes share a subset of configuration options which define
the killing procedure of processes belonging to the unit.
This man page lists the configuration options shared by these five unit types. See systemd.unit(5) for the common options shared by all
unit configuration files, and systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5) and systemd.scope(5) for more
information on the configuration file options specific to each unit type.
The kill procedure configuration options are configured in the [Service], [Socket], [Mount] or [Swap] section, depending on the unit type.
OPTIONS
KillMode=
Specifies how processes of this unit shall be killed. One of control-group, process, mixed, none.
If set to control-group, all remaining processes in the control group of this unit will be killed on unit stop (for services: after the
stop command is executed, as configured with ExecStop=). If set to process, only the main process itself is killed. If set to mixed,
the SIGTERM signal (see below) is sent to the main process while the subsequent SIGKILL signal (see below) is sent to all remaining
processes of the unit's control group. If set to none, no process is killed. In this case, only the stop command will be executed on
unit stop, but no process be killed otherwise. Processes remaining alive after stop are left in their control group and the control
group continues to exist after stop unless it is empty.
Processes will first be terminated via SIGTERM (unless the signal to send is changed via KillSignal=). Optionally, this is immediately
followed by a SIGHUP (if enabled with SendSIGHUP=). If then, after a delay (configured via the TimeoutStopSec= option), processes still
remain, the termination request is repeated with the SIGKILL signal (unless this is disabled via the SendSIGKILL= option). See kill(2)
for more information.
Defaults to control-group.
KillSignal=
Specifies which signal to use when killing a service. This controls the signal that is sent as first step of shutting down a unit (see
above), and is usually followed by SIGKILL (see above and below). For a list of valid signals, see signal(7). Defaults to SIGTERM.
Note that, right after sending the signal specified in this setting, systemd will always send SIGCONT, to ensure that even suspended
tasks can be terminated cleanly.
SendSIGHUP=
Specifies whether to send SIGHUP to remaining processes immediately after sending the signal configured with KillSignal=. This is
useful to indicate to shells and shell-like programs that their connection has been severed. Takes a boolean value. Defaults to "no".
SendSIGKILL=
Specifies whether to send SIGKILL to remaining processes after a timeout, if the normal shutdown procedure left processes of the
service around. Takes a boolean value. Defaults to "yes".
SEE ALSO
systemd(1), systemctl(1), journalctl(8), systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5),
systemd.exec(5), systemd.directives(7), kill(2), signal(7)
systemd 237 SYSTEMD.KILL(5)