I am guessing you used the bfu bits before 10pm US Eastern time on
04/23/2009. It suffered from "8390 'svcadm disable nwam' sends nwam into
maintenance". nwamadm is not sleeping but in a deadlock. This has since
been fixed and I've respun the bfu archives, still dated as
nwam1-build:2009-04-23 (I've deleted the toxic bits).

Anurag

Lizhong Li wrote:
> Hi,
>
> I always use script to setup several profiles, but it will get the
> following error if the 'nwamadm list' is executed immediately, so is it
> reasonable ? or how many seconds should it sleep ?
>
> earthscience:exp# nwamcfg -f nwamadm_create_all.s; nwamadm list
> Configuration read.
> TYPE PROFILE STATE
> ncp User uninitialized
> ncp Automatic uninitialized
> loc NoNet uninitialized
> loc Automatic uninitialized
> loc myloc1 uninitialized
> enm myenm1 uninitialized
> enm myenm2 uninitialized
> earthscience:exp#
> earthscience:exp# cat nwamadm_create_all.s
> #destroy -a
> create ncp User
> create ncu ip myncu1
> set ip-version=ipv4,ipv6
> set ipv4-addrsrc=dhcp
> set ipv6-addrsrc=dhcp
> end
> end
> create loc "myloc1"
> set activation-mode=manual
> set nameservices=nis
> set nameservices-config-file="/etc/nsswitch.nis"
> set nis-nameservice-configsrc=dhcp
> end
> create enm myenm1
> set start="/var/tmp/start_myenm1"
> set stop="/var/tmp/stop_myenm1"
> set activation-mode=manual
> end
> create enm myenm2
> set start="/var/tmp/start_myenm2"
> set stop="/var/tmp/stop_myenm2"
> set activation-mode=manual
> end
> earthscience:exp#
>
>   

Reply via email to