Skip to main content

LINUX How to Control System Processes via SSH

The hearth of each OS are its (apart from the Kernel of course) processes. Linux provides various ways to control the current running processes on the server and we will list a couple of examples to illustrate them. Probably the command you would most often use is the “ps” command which lists all processes based on a certain criteria.
Please note that you can not manipulate the system processes (executing ps, kill, pgrep, top and strace) on the shared server, since your account will not have such privileges.
However, on our dedicated servers you will have root permissions and you will be able to control the system processes.
To list all processes which are started by your user, you can use:
ps x where ps is naturally the command itself and x is the argument we are passing to it.
The result will look like the following one:
PID TTY STAT TIME COMMAND 3735 pts/0 R 0:00 bash 3775 pts/0 R+ 0:00 ps x 5032
? Ss 1:01 wget -mbr --no-passive-ftp….
There are 5 columns in the result, each showing a different set of information. PID shows the process ID number. TTY print the file name of the terminal connected to standard input for that particular process. STAT shows the process state (R means running and S means an interruptible sleep (waiting for an event to complete)).
TIME shows the time the process is running for and COMMAND shows the command itself.
To see the same information (and a bit more) but updated in realtime you can use the following command:
topIn some cases you might need to stop a certain process.
The graceful way to do this is to send a SIGHUP (or SIGTERM) signal to the process and ask it politely to stop itself.
To do this you can use:
kill -15 < pid-ID-number >
or in the above example with the wget process:
kill -15 5032
In some cases however a process can decide to ignore this (graceful) signal.
To kill the process in that case, you can force kill it using:
kill -9 5032
which will send the request directly to the Kernel and cannot be ignored.
A shorter variant of ps with an option to filter the result by process name is “pgrep”.
For example:
pgrep -u root sshd
will only list the processes called sshd and owned (-u argument) by the root user.
Each process will be listed on new line, which allows chaining the commands.
An example of chained commands would be:
strace -p `pgrep -u root sshd`
The above example will run strace command and will attach it to the process (-p argument) returned by the pgrep command.

Comments

Post a Comment

Popular posts from this blog

Lambda Function with Amazon SNS

  Amazon SNS is a service used for push notification. In this chapter, we will explain working of AWS Lambda and Amazon SNS with the help of an example where will perform the following actions − Create Topic in SNS Service and use AWS Lambda Add Topics to CloudWatch Send SNS text message on phone number given. Requisites To create Topic in SNS Service and use AWS Lambda Add Topics to CloudWatch, we need not follow the steps given below − Create Topic in SNS Create Role for permission in IAM Create AWS Lambda Function Publish to topic to activate trigger Check the message details in CloudWatch service. To send SNS text message on phone number given, we need to do the following − Add code in AWS Lambda to send message to your phone. Example In this example, we will create a topic in SNS. When details are entered in the topic to publish, AWS Lambda is triggered. The topic details are logged in CloudWatch and a message is sent on phone by AWS Lambda. Here is a basic block diagram which exp
Post a Comment
Read more

Unix / Linux - Shell Input/Output Redirections

W e will discuss in detail about the Shell input/output redirections. Most Unix system commands take input from your terminal and send the resulting output back to your terminal. A command normally reads its input from the standard input, which happens to be your terminal by default. Similarly, a command normally writes its output to standard output, which is again your terminal by default. Output Redirection The output from a command normally intended for standard output can be easily diverted to a file instead. This capability is known as output redirection. If the notation > file is appended to any command that normally writes its output to standard output, the output of that command will be written to file instead of your terminal. Check the following  who  command which redirects the complete output of the command in the users file. $ who > users Notice that no output appears at the terminal. This is because the output has been redirected from the default standard output dev
Post a Comment
Read more

Unix / Linux - Shell Functions

W e will discuss in detail about the shell functions. Functions enable you to break down the overall functionality of a script into smaller, logical subsections, which can then be called upon to perform their individual tasks when needed. Using functions to perform repetitive tasks is an excellent way to create  code reuse . This is an important part of modern object-oriented programming principles. Shell functions are similar to subroutines, procedures, and functions in other programming languages. Creating Functions To declare a function, simply use the following syntax − function_name () { list of commands } The name of your function is  function_name , and that's what you will use to call it from elsewhere in your scripts. The function name must be followed by parentheses, followed by a list of commands enclosed within braces. Example Following example shows the use of function − #!/bin/sh # Define your function here Hello () { echo "Hello World" } # Invoke yo
Post a Comment
Read more