Zhenghui Xie writes: > >How about splitting that into two services? Have one run early in > >boot and just start the daemon. Have the other dependent on > >device/local (or whatever's required) and do the ifconfig operations. > > > > > > > The problem is that staring the daemon is the only thing need to be > done. When starting the daemon, the daemon calls 'ifconfig -a plumb' > first and cause the problem.
I see. If the daemon must do that, and can't do anything else useful on the system until that plumbing operation is done, then the only option left that makes sense to me is to fix the underlying problem that makes devinfo fail. > Maybe I can write a script to plumb and configure bge0 first, using > information in local /etc files? but in this case, when the daemon > startes later, it will try to plumb bge0 again, will this cause problem? You'll get a harmless error from that. It feels like an overconstrained problem to me. We can't fix devinfo, we can't start until devinfo is ready, and devinfo isn't ready until well after we need to be started. One of those things has to give. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
