On Thu, Apr 09, 2009 at 10:37:31AM -0400, Anurag S. Maskey wrote: > The reason this is failing is because the activation-mode for Legacy is > "system" and the copy cannot have that activation-mode. The error is > not quite helpful as it doesn't say which property value failed > validation. I've logged a task to my list to provide better error > message.
Thanks, Anurag; identifying the problematic property is definitely a good thing to do there. But I'm also wondering if we should have some exception handling for cases such as this. I can definitely see where copying the Legacy location would be useful; would it make sense to allow it to be copied, and just clear out the activation-mode value in the copy? -renee > > Anurag > > > Lizhong Li wrote: >> Hi, >> >> For bits Mar 31, how to make a copy of the Legacy location ? >> >> earthscience:nwam# uname -a >> SunOS earthscience 5.11 nwam1-build:2009-03-31 i86pc i386 i86pc >> earthscience:nwam# nwamcfg list >> NCPs: >> Automatic >> Locations: >> Automatic >> NoNet >> Legacy >> earthscience:nwam# ypwhich >> ypwhich: can't communicate with ypbind >> >> earthscience:nwam# nwamadm enable Legacy >> nwamadm: Only profiles with manual activation-mode can be enabled >> >> earthscience:nwam# >> earthscience:nwam# nwamcfg create -t Legacy loc Legacy2 >> Commit error: validation of entity value failed >> >> I'm curious about this error too, is anything wrong ? >> -- >> Thanks, >> Lizhong >>
