Mailinglist Archive: opensuse-factory (564 mails)
| < Previous | Next > |
Re: [opensuse-factory] Re: Human readable, what is that? (was [12.1] massive data loss in /var/tmp/)
- From: Stefan Seyfried <stefan.seyfried@xxxxxxxxxxxxxx>
- Date: Thu, 29 Dec 2011 09:03:21 +0100
- Message-id: <4EFC1EC9.4080502@message-id.googlemail.com>
Am 29.12.2011 08:50, schrieb Michal Kubeček:
Yes, by rewriting all init scripts. And keeping those patches forever...
"easily" is also something I'd dispute here.
Of course there are services where it does not make sense - and for sshd
it does not happen. But very often it is a must have feature.
--
Stefan Seyfried
"Dispatch war rocket Ajax to bring back his body!"
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
On Wednesday 28 of December 2011 22:25EN, Stefan Seyfried wrote:
Am 28.12.2011 15:49, schrieb Michal Kubeček:
So far, I haven't seen any (useful) feature that systemd would
provide that couldn't be with much less effort achived without it.
Reliably(!) putting each service into its own cgroup.
Reliably stopping a service and all(!) of its children.
I replied to this already. This can be easily done with init scripts as
well
Yes, by rewriting all init scripts. And keeping those patches forever...
"easily" is also something I'd dispute here.
- with much less effort than has been invested into systemd
transition (and without its harmful side effects). Moreover, these
features could be optional as they are not always desirable - for
instance, when restarting sshd, I certainly don't want to kill all its
children.
Of course there are services where it does not make sense - and for sshd
it does not happen. But very often it is a must have feature.
--
Stefan Seyfried
"Dispatch war rocket Ajax to bring back his body!"
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
| < Previous | Next > |