Skip to main content

Checkconfig - configure services start and stop automatically in the /etc/rd.d/init.d

The Chkconfig command tool allows to configure services start and stop automatically in the /etc/rd.d/init.d scripts through command line. Let’s see some examples.

List All services

# chkconfig --list

acpid           0:off   1:off   2:on    3:on    4:on    5:on    6:off
atd             0:off   1:off   2:off   3:on    4:on    5:on    6:off
htcacheclean    0:off   1:off   2:off   3:off   4:off   5:off   6:off
httpd           0:off   1:off   2:off   3:off   4:off   5:off   6:off


Check specific services

# chkconfig --list | grep httpd
httpd           0:off   1:off   2:off   3:off   4:off   5:off   6:off
 
Start Particular Service 


 The command shows how to start HTTP services only on run level 3 and 5 with 


 ‘–level‘ parameter. 


 


# chkconfig --level 35 httpd on  -- starts httpd services on run level 3 and 5


 


# chkconfig --list | grep httpd --verifies the status of httpd services running on run level
httpd           0:off   1:off   2:off   3:on    4:off   5:on    6:off


 


 


# chkconfig --list | grep 5:on


# chkconfig --list | grep 5:off


 


How to stop a particular service on Run Level 




This command will turned Off a service called postfix 


for a just single run level. Similarly, we can turn Off a particular 


service in multiple run levels in one go as shown under.


 


# chkconfig --level 3 postfix off


 


# chkconfig --level 2345 postfix off


 


 


Additional Information:


 


From the file /etc/inittab:

# Default runlevel. The runlevels used by RHS are:

#   0 - halt (Do NOT set initdefault to this)

#   1 - Single user mode

#   2 - Multiuser, without NFS (The same as 3, if you do not have networking)

#   3 - Full multiuser mode

#   4 - unused

#   5 - X11

#   6 - reboot (Do NOT set initdefault to this)



If your system boots with a gui, then you use runlevel 5, if it boots to a text console, you're using runlevel 3.

 


 






 















Labels:




































Comments








Post a Comment
























Popular posts from this blog



















Data Wrangling vs EDA




























  Aspect Data Wrangling (Data Preprocessing) Exploratory Data Analysis (EDA) Objective Prepare raw data for modeling by cleaning, transforming, and formatting it appropriately. Explore and understand the data to gain insights, identify patterns, and make decisions on data handling and modeling. Order Typically performed as a preliminary step before EDA. Usually conducted after data wrangling to further investigate data characteristics. Data Handling Focuses on data cleaning, filling missing values, encoding categorical variables, and scaling features. Involves data visualization, statistical analysis, and summary statistics to uncover patterns, relationships, and anomalies. Techniques Techniques include imputation, outlier detection, feature scaling, and one-hot encoding. Techniques include histograms, scatter plots, box plots, correlation matrices, and descriptive statistics. Data Transformation Involves structural changes to the dataset, such as feature engineering, data normaliz...




















Post a Comment









Read more




























What is Tensor Parallelism and relationship between Buffer and GPU




























  Tensor Parallelism in GPU Tensor parallelism  is a technique used to distribute the computation of large tensor operations across multiple GPUs or multiple cores within a GPU .   It is an essential method for improving the performance and scalability of deep learning models, particularly when dealing with very large models that cannot fit into the memory of a single GPU. Key Concepts Tensor Operations : Tensors are multidimensional arrays used extensively in deep learning.  Common tensor operations include matrix multiplication, convolution, and element-wise operations. Parallelism : Parallelism involves dividing a task into smaller sub-tasks that can be executed simultaneously. This approach leverages the parallel processing capabilities of GPUs to speed up computations. How Tensor Parallelism Works Splitting Tensors : The core idea of tensor parallelism is to split large tensors into smaller chunks that can be processed in parallel. Each chunk is assigned to a different GP...




















Post a Comment









Read more




























Infrastructure limitations ESX Server 4 vs ESXI 5




























Some limitations in ESX Server 4 may constrain the design of data centers:[28][29]   • Guest system maximum RAM: 255 GB  • Host system maximum RAM: 1 TB[28]  • Number of hosts in a high availability cluster: 32  • Number of Primary Nodes in ESX Cluster high availability: 5  • Number of hosts in a Distributed Resource Scheduler cluster: 32  • Maximum number of processors per virtual machine: 8  • Maximum number of processors per host: 160  • Maximum number of cores per processor: 12  • Maximum number of virtual machines per host: 320  • VMFS-3 limits files to 262,144 (218) blocks, which translates to 256 GB for 1 MB block sizes (the default) or up to 2 TB for 8 MB block sizes.[30] However, on a VMFS Boot drive, it is usually very difficult to use anything other than 1 MB Block size [31].   With ESXI 5 there has been some changes to these limits[32]   • Guest system maximum RAM: 1 TB  • Host system maximum RAM: 2 TB  • Number of hosts in a high availability cluster: 32  • Maximum number ...




















Post a Comment









Read more