Dan Groves wrote: > I agree it's something else, but I think we still have a race condition > here. > > linkmgmtd does all of its SMF and door call initialization after it > daemonizes. When linkmgmtd daemonizes, it returns and the SMF start > script for the linkmgmt service continues. SMF could then start nwamd > before linkmgmtd has finished its initialization. ... > We'll need some mechanism to make sure linkmgmtd is finished its > initialization before SMF tries to start other things. I wonder if we > could use the door file for this? Initializing the door is the last > thing linkmgmtd does when it initializes. Say have the start up script > delete the door file, then linkmgmtd will recreate the door file when it > initializes the door, and once the door file exists, the start script > can terminate. We can have the start script give up after a while if > the door file never shows up (to keep from hanging on boot). > > thoughts?
Why not modify linkmgmtd to not daemonize until it has completed its initialization, including door setup? -Seb
