5 Basic chkconfig Command Examples in Linux

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.95/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Ravi Saive

I am Ravi Saive, creator of TecMint. A Computer Geek and Linux Guru who loves to share tricks and tips on Internet. Most Of My Servers runs on Open Source Platform called Linux. Follow Me: Twitter, Facebook and Google+

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

8 Responses

  1. shivendra says:

    wrong path has been gives, please correct it to /etc/rc.d/init.d/

  2. Kandhanadhan says:

    Sir, I need to know the way to find out the service name and daemon name for a particular package. Example for samba package alone, it has to show the service name smb and daemon name smbd.

    Thanks in advance

  3. Glitter says:

    very informative article and simple to understand

  4. shashi says:

    Nice post, thanks.

  5. Sandy6933 says:

    Nice post…Its so easy to understand!

    Thank you very much for the hardwork :)

  6. Keltron3030 says:

    Current Introduction typo to be corrected for directory path of RC scripts; /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.

    Corrected directory path of RC scripts; /etc/rc.d/init.d

  7. Shepp says:

    #2 could be better written as…
    $ chkconfig httpd –list

    6 less keystrokes is a win in my book :)

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *