diff options
Diffstat (limited to 'usr/src/lib/passwdutil')
| -rw-r--r-- | usr/src/lib/passwdutil/files_attr.c | 2 | ||||
| -rw-r--r-- | usr/src/lib/passwdutil/ldap_attr.c | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/usr/src/lib/passwdutil/files_attr.c b/usr/src/lib/passwdutil/files_attr.c index 8a250b90df..c1021b361c 100644 --- a/usr/src/lib/passwdutil/files_attr.c +++ b/usr/src/lib/passwdutil/files_attr.c @@ -1135,7 +1135,7 @@ files_putpwnam(char *name, char *oldpw, pwu_repository_t *rep, void *buf) /* * NOTE: This is all covered under the repository lock held for updating - * passwd(4) and shadow(4). + * passwd(5) and shadow(5). */ int files_update_history(char *name, struct spwd *spwd) diff --git a/usr/src/lib/passwdutil/ldap_attr.c b/usr/src/lib/passwdutil/ldap_attr.c index 4c43eb7adb..42489c8473 100644 --- a/usr/src/lib/passwdutil/ldap_attr.c +++ b/usr/src/lib/passwdutil/ldap_attr.c @@ -181,7 +181,7 @@ free_ldapbuf(ldapbuf_t *p) * * If the Shadow Update functionality is enabled, then we check to * see if the caller has 0 as the euid or has all zone privs. If so, - * the caller would be able to modify shadow(4) data stored on the + * the caller would be able to modify shadow(5) data stored on the * LDAP server. Otherwise, when LDAP Shadow Update is not enabled, * we can't determine whether the user is "privileged" in the LDAP * sense. The operation should be attempted and will succeed if the |