Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Extensions are a human-readable mnemonic. Code should never depend on the presence or absence of an extension. It makes gzip a pain to use. Use chkconfig --list to show the configuration of files in /etc/init.d/
Is the best practice not to use them, or to use them, or to use them just when you want to make it more obvious to a human?
Also, chkconfig doesn't exist. I started with Centos which I did use, but with debian, I thought update-rc was the tool.
init.d is one of the "special" folders that should only hold one type of file (a script) or a link to that kind of file. Nothing in that folder should require an extension, but I would not obsess over it one way or another.
chkconfig is somewhat specific to the Red Hat family of distributions. Moving between a dozen distributions, I use the tools, but often look for myself. That is easy on a system that uses the traditional tools, but I have not fully adjusted to the systemd world just yet and still need the tools on those.
what version of debian are you using? if it is an up-to-date version then it will be using systemd rather than sysvinit which maybe a consideration on how to implement things.
what version of debian are you using? if it is an up-to-date version then it will be using systemd rather than sysvinit which maybe a consideration on how to implement things.
Not sure where that version sits in the scheme of things. According to distrowatch the latest version (2017-04-10) is using systemd, so you would be looking to run systemctl --list-units.
The previous listed version (2015-02-16) is still sysvinit. Of course if it is anything like Oracle linux, they decided to mix the 2 together (sheesh)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.