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


















Labels:




































Comments








Post a Comment
























Popular posts from this blog



















What is the difference between Elastic and Enterprise Redis w.r.t "Hybrid Query" capabilities




























  We'll explore scenarios involving nested queries, aggregations, custom scoring, and hybrid queries that combine multiple search criteria. 1. Nested Queries ElasticSearch Example: ElasticSearch supports nested documents, which allows for querying on nested fields with complex conditions. Query: Find products where the product has a review with a rating of 5 and the review text contains "excellent". {   "query": {     "nested": {       "path": "reviews",       "query": {         "bool": {           "must": [             { "match": { "reviews.rating": 5 } },             { "match": { "reviews.text": "excellent" } }           ]         }       }     }   } } Redis Limitation: Redis does not support nested documents natively. While you can store nested structures in JSON documents using the RedisJSON module, querying these nested structures with complex condi...




















Post a Comment









Read more




























Training LLM model requires more GPU RAM than storing same LLM




























Storing an LLM model and training the same model both require memory, but the memory requirements for training are typically higher than just storing the model. Let's dive into the details: Memory Requirement for Storing the Model: When you store an LLM model, you need to save the weights of the model parameters. Each parameter is typically represented by a 32-bit float (4 bytes). The memory requirement for storing the model weights is calculated by multiplying the number of parameters by 4 bytes. For example, if you have a model with 1 billion parameters, the memory requirement for storing the model weights alone would be 4 GB  (4 bytes * 1 billion parameters). Memory Requirement for Training: During the training process, additional components use GPU memory in addition to the model weights. These components include optimizer states, gradients, activations, and temporary variables needed by the training process. These components can require additional memory beyond just storing th...




















Post a Comment









Read more




























How are vector databases used?




























  Vector Databases Usage: Typically used for vector search use cases such as visual, semantic, and multimodal search. More recently, they are paired with generative AI text models for conversational search experiences. Development Process: Begins with building an embedding model designed to encode a corpus (e.g., product images) into vectors. The data import process is referred to as data hydration. Application Development: Application developers utilize the database to search for similar products. This involves encoding a product image and using the vector to query for similar images. k-Nearest Neighbor (k-NN) Indexes: Within the model, k-nearest neighbor (k-NN) indexes facilitate efficient retrieval of vectors. A distance function like cosine is applied to rank results by similarity.




















Post a Comment









Read more