Tim Haley - Sun Microsystem writes: > I am sponsoring the following fast-track for Keyur Desai. The > requested binding is micro, timeout 4/22/2008.
Is "patch/micro" intended? If so, then what happens when someone with one of the existing systems gets this new implementation? What does patch installation do? > Exported Interfaces > -------------------- > - libnbt.so Exported how? What stability do these interfaces have? Does anything use them? (Are they present on any other systems?) If these are intended to be something other than "Project Private," could we have a list of the interfaces in the library? > SYNOPSIS > /usr/lib/smbsrv/nbtd Are users or scripts supposed to interact directly with the binary? If not, then why document it? I suspect that this should actually be a Project Private detail, and that the SMF FMRI is the documented administrative interface. > EXIT STATUS > > The following exit values are returned: Similarly, I don't think these should be public interfaces, unless there's some clear need for some other part of the system to invoke the daemon directly. If there is such a need, then that's an important bit of architecture to discuss. (And, if so, this might not be a fast-track anymore.) > Use the svcadm command to perform administrative actions on > the nbtd service, such as enabling, disabling, or restarting > the service. Use the svcs command to query the service > status. 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)? -- 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
