Peter Memishian writes: > > > > If the old ndd commands to display these tables (tcp_conn_hash, > > > tcp_bind_hash, tcp_acceptor_hash, tcp_listen_hash, udp_bind_hash) are > > > not necessary, then I can just remove those commands. > > > > The point in moving this stuff from ndd to mdb is not to just > > translate the existing ad-hoc ndd interfaces verbatim, but to make > > sure that the same data is reasonably available: > > > > - For data items that are already printed by "netstat" or some other > > utility, that portion of the ndd output can be removed without > > touching mdb. (Mirroring the user-level bit into mdb is nice, but > > not necessary.) > > I may have missed some context here, but it seems more than nice in that > it enables one to conveniently get that information from a crash dump. In > other words, I don't think presence of a userland utility is the only (or > even primary) factor; it's really about how important the information is > to someone diagnosing a problem using the dump.
You're right about the usefulness in mdb. I was jumping back to CR 4616660 and the basis for yanking the ndd cruft. All it needs is a display method. CR 6806928 is icing. -- James Carlson, Solaris Networking <[email protected]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
