Quoth andrew rutz on Mon, Jun 11, 2007 at 09:29:40PM -0500: > so, it seems i need to change picld's dependency. does this require > an ARC case?
No. Unless the providing service is private, I suppose. > also, what's the "spirit" of nominating a dependency? eg, fine-grain > vs coarse-grain: eg, milestone/devices completes even later than > syseventd, and (for a user/programmer) it probably is more > semantically-intuitive to link picld w/ a device Milestone (as picld's > job is to rummage around all the devs...) or... is it better to make > a finer-grained dependency and link picld to syseventd because that > literally is what it's dependent on? Well if syseventd were replaced by something better, would picld have to be rewritten? That is, does it communicate specifically with syseventd, or indirectly through generic interfaces? > ...and if you answer "syseventd" ;-) ...then i'm back in the same boat, > cuz syseventd forks and the parent returns ... and the child remains > as a daemon... and the child doesn't announce that it can handle > sysevents till essentially the last step in its init'ing. ...so there's > a race between setting of sysevent_daemon_init global and the calling > of i_ddi_io_initialized(). Sorry I don't know the details of syseventd, but if its start method returns success before it is capable of servicing requests, then that's a bug in syseventd. David
