Change Is Inevitable
  • Home
  • MySQL
    • MySQL-Articles
    • AWS RDS
    • Percona Xtradb Cluster
    • MariaDB
    • Galera Cluster
    • ProxySQL
    • MySQL-Scripts
    • MySQL tools
    • MySQL Resources
  • Tools
    • MySQL Advisor
    • MySQL Random Data Generator
    • Postgresql Random Data Generator
    • Clean Prompt
  • General
    • binary-to-decimal
    • Fermat’s Theorem
    • Review
    • Just for fun
    • Personal
  • Contact Me
    • Copyright
    • MySQL Podcast (Youtube)
    • MySQL Podcast (Spotify)
Recent Posts
  • MySQL INSTANT DDL breaks EXCHANGE PARTITION
  • How to setup and use Percona Binlog Server (PBS)
  • MySQL Major Version Upgrade Checklist – how to
  • InnoDB Flushing is simple – explained
  • MySQL Tools for Performance Tuning and Test Data Generation
Recent Comments
  • Kedar on MySQL INSTANT DDL breaks EXCHANGE PARTITION
  • Jean-François Gagné on MySQL INSTANT DDL breaks EXCHANGE PARTITION
  • Reggie on A Unique Foreign Key issue in MySQL 8.4
  • Kedar on How to fix write latency in MySQL 8.4 Upgrade
  • Kedar on How to fix write latency in MySQL 8.4 Upgrade
Home » MySQL » MySQL-Articles » MySQL 8 Resource Group – introduction and dynamic allocation » Page 11
Change Is Inevitable

Kedar Vaijanapurkar's Blog for MySQL, technology and various subjects

  • Home
  • MySQL
    • MySQL-Articles
    • AWS RDS
    • Percona Xtradb Cluster
    • MariaDB
    • Galera Cluster
    • ProxySQL
    • MySQL-Scripts
    • MySQL tools
    • MySQL Resources
  • Tools
    • MySQL Advisor
    • MySQL Random Data Generator
    • Postgresql Random Data Generator
    • Clean Prompt
  • General
    • binary-to-decimal
    • Fermat’s Theorem
    • Review
    • Just for fun
    • Personal
  • Contact Me
    • Copyright
    • MySQL Podcast (Youtube)
    • MySQL Podcast (Spotify)

MySQL 8 Resource Group – introduction and dynamic allocation

  • September 7, 2018
Introduction to resource groups in MySQL 8 and dynamical allocation to threads
View Post

Galera cluster to AWS Aurora migration & HA_ERR_FOUND_DUPP_KEY

  • August 13, 2018
In this post we will see a case study of a Galera Cluster migration to AWS Aurora and quick solution to the replication issue. A friend received an error in…
View Post

Restore A Table / Database From Full Backup – Yet Another Way

  • June 29, 2018
How to Restore A Table / Database From Full Backup using MySQL Grants & mysqldump.
View Post

Export MySQL database table to CSV (delimited / Excel) file

  • January 29, 2018
Today lets talk a little about converting a MySQL table to CSV (Excel). My friend was looking to export MySQL to Excel, I saw couple of questions for export MySQL…
View Post

A tale of Corrupt InnoDB table, MySQL crash & recovery

  • January 18, 2018
I’m going to narrate you a story that happened around a crashing MyQL, Corrupted InnoDB table and finally the recovery by table restore. We will see how our database administrator…
View Post

How to Pause (Suspend) a process in Linux with kill signals

  • January 9, 2018
In this post we will see how to pause (suspend) and start a linux process using signals (SIGTSTP and SIGCONT) via kill command.
View Post

Posts pagination

Previous 1 … 10 11 12 … 36 Next
MySQL Podcast (Youtube)
RSS feed: MySQL Podcast (Spotify) MySQL Podcast (Spotify)
  • MySQL Major Version Upgrade Checklist (Zero Downtime Strategy)
    Upgrading MySQL major versions in production is never just a version bump - it’s a carefully planned process involving compatibility checks, replication strategy, testing, and controlled cut-over.In this episode, we walk through a practical MySQL Major Version Upgrade Checklist based on real-world DBA workflows. We are covering MySQL replication as base setup for upgrade. It […]
Search:
... ...
  • MySQL INSTANT DDL breaks EXCHANGE PARTITION
  • How to setup and use Percona Binlog Server (PBS)
  • MySQL Major Version Upgrade Checklist – how to
  • InnoDB Flushing is simple – explained
  • MySQL Tools for Performance Tuning and Test Data Generation

2 responses to “How to Pause (Suspend) a process in Linux with kill signals”

  1. Richard Avatar
    Richard
    June 16, 2025

    Hi there,

    Your script could be improved somewhat, because if you only give it ‘start’ or ‘stop’ as parameter without a second parameter, it will happily execute a kill command, which will fail because the PID is missing.

    For that, I suggest changing the line ‘if [ “$#” -eq 0 ]; then’ to ‘if [ “$#” -lt 2 ]; then’.

    Secondly, the line under ‘usage() {‘ isn’t quite correct. I would suggest the following:
    echo “$(basename $0) [stop|start] PID”

    This way, the actual script name is shown, while the ‘basename’ makes sure the path to the script is left out.

    Lastly, the semicolon after the last line isn’t necessary and looks a bit wacky because there is another line with ‘fi’ that isn’t followed by a semicolon, so the last line looks out of place.

    Reply
    1. Kedar Avatar
      Kedar
      September 13, 2025

      Thank you for your inputs, Richard,
      I was working on a PoC for something and this was one of the section of that which I found useful to share. That said, your recommendations are good. I will look to adjust this.
      Cheers.

      Reply
Change Is Inevitable
Designed & Developed by Code Supply Co.