sowmini.varadhan at sun.com wrote: > On (03/10/09 13:13), Paul Durrant wrote: >> How about deliberately making sure that the per-interface props. are >> differently names to global props. already available via ndd and giving >> per-interface props. the possibility of being undefined. Then: > > that still leaves a mess in the kernel (and even in the user-semantics). > Let's take the icmp error rate limit as an example. If I say > > # ipadm set-prop -p icmp_err_rate_limit=val1 bge0 > # ipadm set-prop -p icmp_err_rate_limit=val2 bge0 > > while supporting the > # ndd -[set,get] /dev/ip old_icmp_err_rate_limit <..> > > what is the kernel going to track for the older "global" definition? > No matter what I print for the global "ndd -get" value, it's going to > be a lie. >
Why would it be a lie? There is a prop. caller old_icmp_err_rate_limit and you can print its value. However, neither bge0 not bge1 use it. Why is that a problem? ndd is marked as deprecated, so surely it's 'user beware'? Paul -- =================================== Paul Durrant http://www.linkedin.com/in/pdurrant ===================================
