[SOLVED] systemd and server maintainability for future libraries/programs
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
systemd and server maintainability for future libraries/programs
This is question about systemd stability/maintainability for servers.
This is not about your opinions on systemd.
I would like to use Alpine Linux for my server, however, it does not use systemd. Will this present a problem in the next few years? Meaning, will the lack of systemd present startup issues for things like databases, web servers, mounting hard drives, RAID drives on start up?
I currently use PHP-FPM + nGinx + MySQL
I compile PHP-FPM from source, and would like to continue starting the binary before nGinx starts up. I'm using upstart on my current server and have no problems. However, I don't know if the programs I rely upon will take advantage of systemd in a way that will break my current system.
I'm not a sys admin, I'm a developer, who has some sys admin skills, but mostly, I just want to get stuff done.
Unless Gentoo decides to abandon OpenRC, it should be quite reliable, and the Gentoo community is very strong and very committed to Gentoo. This article may help: https://iwf1.com/systemd-vs-openrc-w...you-comparison
I would like to use Alpine Linux for my server, however, it does not use [...]. Will this present a problem in the next few years? Meaning, will the lack of [...] present startup issues for things like databases, web servers, mounting hard drives, RAID drives on start up?
The question should be framed in the context of OpenRC then, instead of baiting.
The short answer is no, the package maintainers for the Alpine Linux repositories take care of making sure there are scripts to start, stop, and check on daemons. The longer answer is probably not, as long as upstream packages maintain independence and don't go like Gnome went there won't be issues.
I actually didn't know that Alpine used OpenRC. I was just looking for a good small distro for a web-server to replace by Ubuntu 14 box, and trying to get some info
I just wanted to make sure that MySQL/Nginx weren't going to do anything to take advantage of one init system over another, and also make sure I could mount drives, external drives without issues.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.