|
Enhanced in NETDB.NLM 4.10x:
The /N parameter on NETDB was expanded to suppress a search method (introduced in v4.10o) for the Unix Service Handler. The /N was preventing login, but not the new search. Now both are supressed by /N.
Additionally, the /N functionality can be obtained without any command line parameter. This will help eliminate the concern that some other NLM may auto-load NETDB before the explicit LOAD NETDB /N is done. To do this, edit or create the file SYS:ETC\NWPARAMS. Go to (or create) a label:
[NETDB]
Under that, add the line:
LOGIN_TO_NDS 0
(that's a zero). This will trigger the /N functionality even if the /N was not given on the command line. If this setting is not present, or if it is set to 1 (one), then the normal behavior will occur. (Normal behavior: NETDB will attempt to search and login, unless /N is given. /N can still override a setting of 1.)
Previously fixed in 4.10s:
Made a change to NETDB to prevent an NISBIND hang while unloading.
Previously fixed in 4.10q:
Server would abend upon loading NETDB if the SYS:ETC\RESOLV.CFG file contained a nameserver entry without a space character. An example of the proper format of the RESOLV.CFG file is:
domain mydomain.com
nameserver 10.11.12.13
nameserver 192.168.1.2
Now if NETDB finds a nameserver entry without a space, it will ignore the entry rather than abend.
Previously fixed in 4.10p:
If NFS 3.0 was set to be an NIS Client to itself, the NIS client access would fail, and the server would abend upon NFSSTOP. This has been corrected.
Previously fixed in 4.10o:
NETDB was not able to use a NWPARAMS file NDS_CONTEXT that included a Country (C=) container. This has been corrected.
NETDB's NDS login method has been redesigned to use less expensive DS queries, and to do them less often. Some systems where NETDB login was not required, and which didn't have a UNIX Service Handler user (which NETDB uses) were experiencing unnecessary DS or processor utilization while NETDB continued to search for this user. Some administrators have been loading NETDB with the /N parameter (no login) to avoid this issue. NETDB was previously attempting to login every 10 seconds until the UNIX Service Handler was found. It was not making any attempt to verify that the object existed before the login attempt was made. Now, the login is not attempted until after the object is found. Furthermore, the search process will only occur every 60 seconds. (The /N parameter is still available to prevent the logion process completely).
|
