Mailinglist Archive: opensuse-factory (564 mails)
| < Previous | Next > |
[opensuse-factory] Re: Human readable, what is that? (was [12.1] massive data loss in /var/tmp/)
- From: Joachim Schrod <jschrod@xxxxxxx>
- Date: Thu, 29 Dec 2011 14:41:44 +0100
- Message-id: <jdhqmp$sat$1@dough.gmane.org>
Cristian Rodríguez wrote:
That was not the use case for ExecStatus
The presented use cases were (a) services that have no master
daemon process, but a set of processes. VM instances, or LXC
containers were explicitly presented. And (b) services where the
state can be changed by control commands without involvement of any
daemon and thus there is no daemon that one can query for the
current service status.
In our customers' environment, both use cases happen quite often.
You are quick to dismiss arguments, like in your *very* polemic
answer to Christian's AppArmor arguments, without providing an
explanation how these two use cases shall be handled with the
current systemd framework; without introducing watchdog processes
because upstream wouldn't implement them just for the sake of systemd.
Joachim
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: jschrod@xxxxxxx
Roedermark, Germany
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
I am talking about
requests that ask for systemd to manage services that do not
provide proper exit status codes.
That was not the use case for ExecStatus
The presented use cases were (a) services that have no master
daemon process, but a set of processes. VM instances, or LXC
containers were explicitly presented. And (b) services where the
state can be changed by control commands without involvement of any
daemon and thus there is no daemon that one can query for the
current service status.
In our customers' environment, both use cases happen quite often.
You are quick to dismiss arguments, like in your *very* polemic
answer to Christian's AppArmor arguments, without providing an
explanation how these two use cases shall be handled with the
current systemd framework; without introducing watchdog processes
because upstream wouldn't implement them just for the sake of systemd.
Joachim
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: jschrod@xxxxxxx
Roedermark, Germany
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
| < Previous | Next > |