To completely convert your site to NIS+, you must both change the name service and port all applications to NIS+. Any internally created applications that make NIS calls have to be modified to use NIS+ calls. Otherwise, you always have to run your NIS+ servers in NIS-compatibility mode, with all the drawbacks that this mode entails. External applications may force you to run your namespace in NIS-compatibility mode until they are updated, as well.
Table 4-5 contains a list of the NIS API functions and their NIS+ API equivalents, if they exist.
Table 4-5 NIS API and NIS+ API Equivalent Functions
NIS API Functions |
NIS+ API Functions |
---|---|
yp_get_default_domain() |
nis_local_directory() |
ypbind() |
N/A |
ypunbind() |
N/A |
ypmatch() |
nis_list() |
yp_first() |
nis_first_entry() |
yp_next() |
nis_next_entry() |
yp_all() |
nis_list() |
yp_master() |
nis_lookup() |
yperr_string() |
nis_perror() nis_sperrno() |
ypprot_err() |
nis_perror() nis_sperrno() |
yp_order() |
N/A |
yp_update() |
nis_add_entry(), nis_remove_entry(), nis_modify_entry() |