On (03/10/09 13:21), Paul Durrant wrote: >> 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'?
catching up on this thread (which progressed a bit while I wasn't looking)- I see what you/Jim mean: basically redefine ndd variables as "values that would be configured unless they are over-ridden by per-interface specific props from ipadm" And it wouldn't be too hard to implement Jim's (b) suggestion- we'd have to track a dont_use_ndd_global_default bit per interface, per property. Yes, that is feasible, and probably better than 1-4 in my list. --Sowmini
