4 ms·
> Managing services on CentOS is the same as managing them on Debian which is the same as managing them on OpenSUSE. It's not really the same, some systemd-bas
by zzzcpan 7y ago
> Managing services on CentOS is the same as managing them on Debian which is the same as managing them on OpenSUSE.
It's not really the same, some systemd-based distros diverge a lot and anything non-systemd much more so, including FreeBSD. Even something as basic as network configuration could be completely different on systemd distros, like Ubuntu with its netplan weirdness and Archlinux going into the opposite direction and forcing you to choose how to deal with network yourself from the start.
But still, if you want any sanity in your deployment across different distros - you simply have to avoid using systemd or other host's init and service management systems for anything and bring your own service management with you. It could be as simple as a script starting from root's cron at @reboot (this particular trick survived for decades for example).
- Spivak 7y ago> But still, if you want any sanity in your deployment across different distros This might be true for your in-house app but if you want sanity in packaging your service for inclusion in various distros you include a .service file.
- Mister_Snuggles 7y agoBy managing services I really mean starting/stopping/checking status of/etc daemons. On a systemd distribution, you make a unit file that describes the daemon and use systemctl to manage it. It seems like sanity for deployment can be accomplished by delivering a template unit file and letting the distro maintainer or sysadmin customize it as required. Networking is a little out of scope here - I'd guess that changing basic network configuration is something that's less frequent than the service management tasks.