Keyur Desai writes: > >> Are users or scripts supposed to interact directly with the binary? > >> If not, then why document it? > >> > > I'll let Keyur confirm, but I don't believe so. It was included for > > completeness more than anything. > > That is correct. The nbtd(1M) and the nbt(4) man pages were included for > completeness purposes.
OK. Then what are users told? > >> Who enables this? Is the administrator expected to know when to do > >> this, or does it get enabled automatically when needed (when sharectl > >> demands it)? > >> > > nbtd daemon is disabled by default. Most administrators know if they > need to enable/disable NetBIOS protocol in their network. You said above that the man pages shown here won't be delivered. So how do users know that "nbtd" is NetBIOS, and how do they know when they need to enable the service? > Some scenarios to enable NetBIOS include, having a system in a network, > which has NT 4.0 (and/or previous) OS installed, or systems > not upgraded to ADS. Sure ... but that translates into knowing "I need NetBIOS," not into "I need to issue 'svcadm enable nbtd' in order to finish configuration." How do users figure that part out? > Some administrators choose to disable NetBIOS from their network, > in order to reduce network traffic caused by periodic host announcements. No doubt. NetBIOS is chatty. > Enabling/disabling of this daemon is at the discretion of the administrator. I'm asking about what documentation might be provided that tells them that they need to do this or (alternatively) how the service can be managed automatically based on the system configuration. If you can do the latter, then there might not be a need for the former. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> 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
