Skip to main content

Initial Settings : Services

 [1]. It's possible to display services' status like follows.

# the list of services that are active now

[root@dlp ~]# systemctl -t service

UNIT                            LOAD   ACTIVE SUB     DESCRIPTION

atd.service                     loaded active running Job spooling tools

auditd.service                  loaded active running Security Auditing Service

chronyd.service                 loaded active running NTP client/server

crond.service                   loaded active running Command Scheduler

dbus.service                    loaded active running D-Bus System Message Bus

.....

.....

user-runtime-dir@0.service      loaded active exited  /run/user/0 mount wrapper

user@0.service                  loaded active running User Manager for UID 0

vdo.service                     loaded active exited  VDO volume services


LOAD   = Reflects whether the unit definition was properly loaded.

ACTIVE = The high-level unit activation state, i.e. generalization of SUB.

SUB    = The low-level unit activation state, values depend on unit type.


45 loaded units listed. Pass --all to see loaded but inactive units, too.

To show all installed unit files use 'systemctl list-unit-files'.


# list of all services

[root@dlp ~]# systemctl list-unit-files -t service

UNIT FILE                                   STATE

arp-ethers.service                          disabled

atd.service                                 enabled

auditd.service                              enabled

autovt@.service                             enabled

blk-availability.service                    disabled

.....

.....

user-runtime-dir@.service                   static

user@.service                               static

vdo.service                                 enabled


181 unit files listed.

[2]. Stop and turn OFF auto-start setting for a service if you don'd need it. (it's smartd as an example below)

[root@dlp ~]# systemctl stop smartd

[root@dlp ~]# systemctl disable smartd

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 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

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