On Tuesday 19 July 2005 12:42 pm, Eric Brown wrote: > The real problem is not that the daemons don't return errors, but that > our init scripts do not make reasonable attempts to verify service startup.
i'd disagree ... if a service sucks, it sucks adding some code to try and guess whether the service actually started is a roundabout (and by no means fool proof) way of doing things ... it may result in correct results sometimes, but i imagine it'll also be susceptible to false positives > If a Gentoo init script claims that a service started, it should make an > effort to check that the processes are actually running shortly after the > script is run how do you define 'short' ? really anything that relies on sometime out value like this is a flawed design ... just cause your smokin fast amd64 should complete in .1 seconds doesnt mean my not-very-smokin-fast-at-all arm netwinder can complete inside of 3 seconds > Relying on the return > value of start-stop-daemon is simply insufficient for some services. then those services should not be using ssd > I propose increasing developer awareness of this problem, perhaps > through some formal guidelines for ebuild developers. this seems to be the only feasible approach (and one i'm all for) -mike -- [email protected] mailing list
