On Wed, 24.08.11 10:10, Jesse Keating (jkeating(a)j2solutions.net) wrote:
>> FWIW, I do think that there may be use-cases for socket
activation of a
>> database. I'd like to support the option ... the problem is to do so
>> without breaking existing, expected behaviors.
>
> It was noted up-thread that systemd can tell you whether the underlying
> daemon is running or not, though I guess that doesn't tell you whether
> it's entirely in a functional state. You could do a two-stage thing:
> check with systemd whether the daemon is running, and ping it if so?
Some of the argument here is that it is difficult to do this from a
remote host. You'd have to engage in remote execution of software,
e.g. using nagios nrpe to remotely (from the nagios system) execute
commands on the database system to call systemd to check the status of
the db.
systemctl actually knows the -H switch to access remote systems (via
ssh), but this needs a patch to dbus to actually work which I still
haven't found time to ultimately clean up for proper inclusion.
Lennart
--
Lennart Poettering - Red Hat, Inc.