> > > > It is impossible to report whether start was OK in a _timely_ fashion > > > > and without false positive. > > > > Some daemons can run for like 20 or 30 seconds spawning stuffs, making > > > > checks... then exiting because there is in fact a problem. > > > > See comments line 121 and 122. "ok" means the daemon was started and > > > > return code was ok. > > > > > > Well, I still think it would be worth to add rc_check after rc_start, > > > even I understand > > > your argument about false positive. > > > > This has been discussed in the past already and we will not add it. > > This could potentially delay the startup bu a _big_ amount of time. > > OK.
Thing is that rc.d(8) is meant to be as simple and generic as possible. Also don't forget both system and ports use this so each function has been carefully though. The drawback is that yes, sometimes it is a little too generic for each and every need, but on the other end, because it is so simple, it's very easy to tweak function(s) _within_ the daemon script itself if more extensive checks are needed (using rc_pre or even rc_start). So it is easily extensible on a case by case basis and we can keep the framework clean and simple. -- Antoine
