Anurag,

I got some odd results while debuging the test cases. It seems like that
'destroy -a' doesn't work correctly in command-file mode.

Here is the script file using for 'nwamcfg -f ...'

    :exp$ cat nwamadm_create_all.s
    destroy -a
    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

    firering:exp# nwamcfg -f nwamadm_create_all.s
    Configuration read.
    firering:exp# nwamadm list
    TYPE PROFILE STATE
    ncp User inactive
    ncp Automatic active
    loc myloc1 inactive
    enm myenm1 inactive
    enm myenm2 inactive
    firering:exp#
    firering:exp# nwamadm enable myenm1
    Enabling enm 'myenm1'
    firering:exp# nwamadm list
    TYPE PROFILE STATE
    ncp User inactive
    ncp Automatic active
    loc myloc1 inactive
    enm myenm2 inactive
    enm myenm1 active

These are right.

    firering:exp# nwamcfg -f nwamadm_create_all.s
    Configuration read.
    firering:exp# nwamadm list
    TYPE PROFILE STATE
    ncp User inactive
    ncp Automatic active
    loc myloc1 inactive
    enm myenm1 active
    enm myenm2 inactive

Now the issue is here, it seems like 'destroy -a' in
nwamadm_create_all.s is not effective, but after about 10 secs the
'myenm1' turns into 'inactive', why ?

While it works right in interactive mode.



-- 
Thanks,
Lizhong


Reply via email to