Consider this shell output and executed commands: [root@oel7 ~]# ps aux | grep mysqld mysql 2076 3.5 24.6 1386852 372572 ? Ssl 12:01 0:01 /usr/sbin/mysqid [root@oel7 ~]# kill -15 2076 Which…

Question

Options

• Akill -15 should be avoided. Use other methods such as mysqladmin shutdown or systemctl stop
• Bkill -15 and kill -9 are effectively the same forced shutdown that risk committed transactions not
• Ckill -15 carries out a normal shutdown process, such as mysqladmin shutdown.
• Dmysqld_safe prohibits commands that would harm the operation of the server. An error would be

• A
  2% (1)
• B
  3% (2)
• C
  95% (57)

Explanation

kill -15 sends the SIGTERM signal, which MySQL's mysqld handles by triggering its built-in graceful shutdown routine - flushing buffers, completing in-flight transactions, and closing connections cleanly. This behavior is identical to what mysqladmin shutdown or systemctl stop invokes, making C correct.

Why the distractors are wrong:

• A is wrong because kill -15 is not dangerous and is a perfectly valid shutdown method - there is no reason to avoid it.
• B is wrong because kill -15 (SIGTERM) and kill -9 (SIGKILL) are fundamentally different: SIGKILL forcefully terminates the process with no cleanup, risking data corruption, while SIGTERM allows controlled shutdown.
• D is wrong because mysqld_safe acts as a watchdog that restarts mysqld if it stops unexpectedly - it does not intercept or block kill signals.

Memory tip: Think of signal numbers: 15 = fifteen = "finish gracefully" (SIGTERM lets the process say goodbye), while 9 = "nein!" = no escape (SIGKILL gives the process no chance to clean up). For MySQL specifically, any graceful shutdown path - whether mysqladmin, systemctl, or kill -15 - all end up triggering the same internal shutdown handler in mysqld.

No community discussion yet for this question.