В Fri, 26 Jun 2015 10:02:41 -0500 Lesley Kimmel <ljkimme...@hotmail.com> пишет:
> Thanks for the information. I've seen that blog before. Unfortunately, it > only describes a starting a service that already has a good level of > integration with some of the underlying infrastructure of systemd (e.g. > dbus). Let me be a little more specific about what I'm trying to accomplish > and see if anyone has any thoughts on how systemd could help (or impede me). > > I have a collection of servers hosting many processes such as Apache HTTPD, a > database, and Java application servers. Using init these servers would: a) > need to be started in a specific order and b) take a long time to start. To > improve both of these scenarios I created a Python service which took an XML > configuration file describing the dependencies of the various components. The > Python service is started by init and forks so as to not stop the boot > process. The forked process then does some basic dependency checking > (including remote tests, mostly telnet or pings) before starting local > services using init scripts that are not configured to be started by init. That sounds exactly like what pacemaker does. > > I'm wondering, with systemd, if this Python "control" daemon would be > required at all. Does systemd have the ability to check the status of remote > servers? No. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
