On Sat, Jun 13, 2015 at 08:40:27AM +0200, Didier Kryn wrote:

[cut]

>

>     The question now is who will develop, maintain and package this
> wrapper? Will Devuan be the official developper of
> "Systemd-Readyness-Wrapper", or can anyone convince Openssh or who
> else to take the job? Or are the daemon's developper powerfull
> enough to tell RH "do it yourself."?

>

I think there is another, more fundamental question: do we really need
to know in *real time* when a service/daemon is ready for its job or
has done what it is supposed to do? AFAIK all this fuss with
"daemon-readiness" began with the first attempts to have parallel boot
sequences, which is something that is still *useless* in 95% of the
use cases: servers don't get restarted evey other minute and "normal"
users who don't use suspend can wait 30 seconds to have their desktop
ready, what else? Embedded systems? Well, they usually have just a few
services running, if any....

What are we really talking about? Isn't this just another
feature-for-the-feature's-sake-thing? Why should I bother to allow
cups signalling immediately that it is ready to put my printouts on a
queue that will anyway need minutes to be processed?

My2Cents

KatolaZ

--
[ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ]
[ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ]
[ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ]
[ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ]