Anurag S. Maskey wrote: > svc:/network/netcfg:default needs to be running if nwamcfg is to be > used. This is very new from the latest build. svc:/network/physical:nwam > depends on network/netcfg. > > The manifest for network/netcfg is "enabled" by default, so I am > surprised why it didn't start on boot. I did experience this same thing > after a BFU and reboot. When I reboot again (2nd time), netcfg started > by default. > > Anyone else the same behavior after rebooting from the bfu# prompt? > > I suspect the problem is with manifest-import - this is the service that adds new services discovered under /var/svc/manifest to the SMF repository. It probably hasn't run by the time the service is needed, so netcfg isn't there yet in the repository. The Clearview folks had a similar issue with the datalink-management service I recall - it'd probably be worth revisiting how they handled this.
Alan > Anurag > > > Lizhong Li wrote: > >> Anurag, >> >> I got the following error : >> >> nwamcfg> create ncp myncp1 >> Create ncp error: could not bind to backend server >> >> firering:exp# uname -a >> SunOS firering 5.11 nwam1-build:2008-12-16 sun4u sparc >> SUNW,Sun-Fire-V215 >> >> Did I miss something ? >> >> >> > _______________________________________________ > nwam-dev mailing list > nwam-dev at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/nwam-dev >
