Most Linux's up until about the 2011-2012 time line used something called sysV init. Some people call it rc or rc.d init.
But about this time most of the major distro's started moving over to something called systemd. Fedora was the first, and then
the same year Debian and Ubuntu joined in. Many distro's used a hybrid approach for a while. Some services still used rc.init
files and some used the systemd.servce files. Some distro's still support backwards compatibility for sysV init, but it's becoming
more and more rare. Even the tradition UNIX's like Solaris and AIX have moved to systemd.
systemd is a lot more flexible and powerful, but there is a little bt of a learning curve. However once you get used to it, it's pretty
easy to use. Just about all major packages install systemd service files by default these days. Even if you download a package from
apache, postgresql, elasticsearch, nginx, docker, or just about anywhere these days... it will have a systemd service file.
You can see what systemd service files are installed on your Linux system by using this command.
In my case, I have over 560 service files installed on my computer.
Unlike NetworkManager, which doesn't like you to manually edit the connection files by hand. Systemd actually wants you to edit
the service files, and it's encouraged to learn how. I do recommend backing up any systemd service that you edit, so that if you
break it, you have something to fall back to. Service files are "usually" kept under either /lib/systemd/system or in my case /usr/lib/systemd/system. Some packages install their service files under /etc/systemd/system. It's bad enough trying to get a the distro's to put the service
files in the same place, but what makes this harder, is all the 3rd party packages that aren't maintained by a specific distro.
.. to be continued.
But about this time most of the major distro's started moving over to something called systemd. Fedora was the first, and then
the same year Debian and Ubuntu joined in. Many distro's used a hybrid approach for a while. Some services still used rc.init
files and some used the systemd.servce files. Some distro's still support backwards compatibility for sysV init, but it's becoming
more and more rare. Even the tradition UNIX's like Solaris and AIX have moved to systemd.
systemd is a lot more flexible and powerful, but there is a little bt of a learning curve. However once you get used to it, it's pretty
easy to use. Just about all major packages install systemd service files by default these days. Even if you download a package from
apache, postgresql, elasticsearch, nginx, docker, or just about anywhere these days... it will have a systemd service file.
You can see what systemd service files are installed on your Linux system by using this command.
Code:
systemctl list-unit-files
In my case, I have over 560 service files installed on my computer.
Unlike NetworkManager, which doesn't like you to manually edit the connection files by hand. Systemd actually wants you to edit
the service files, and it's encouraged to learn how. I do recommend backing up any systemd service that you edit, so that if you
break it, you have something to fall back to. Service files are "usually" kept under either /lib/systemd/system or in my case /usr/lib/systemd/system. Some packages install their service files under /etc/systemd/system. It's bad enough trying to get a the distro's to put the service
files in the same place, but what makes this harder, is all the 3rd party packages that aren't maintained by a specific distro.
.. to be continued.