Bug 64788 - [nsswitch.conf] nsswitch with ldap and starting ppp on boot gives errors
Summary: [nsswitch.conf] nsswitch with ldap and starting ppp on boot gives errors
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 5.2.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-26 22:50 UTC by Antoine Jacoutot
Modified: 2017-12-31 22:35 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Antoine Jacoutot 2004-03-26 22:50:20 UTC 

When using ldap as an authentication mechanism (pam_ldap) and nss_ldap for user info, starting ppp automatically on boot gives the following error:
kernel su: NSSWITCH(nss_method_lookup): ldap, group, setgrent, not found
kernel su: NSSWITCH(nss_method_lookup): ldap, group, getgrent_r, not found
kernel su: NSSWITCH(nss_method_lookup): ldap, group, endgrent, not found

This is due to the fact that /etc/rc.d/ppp-user launches the following command:
su -m ${ppp_user} -c "exec ${ppp_command}"

And at this time, the ldap server is not started yet which means nsswitch cannot access it (for "su" infos).
Note that it does not avoid the connexion to be established (if ppp-user is root), so this might be more a cosmetic fix than a real problem, but I still it should be fixed though.

Fix: 

Make sure the ldap server (slapd) is started BEFORE ppp.
How-To-Repeat: 

Install and configure pam_ldap and nss_ldap for authentication and start ppp on boot (in rc.conf).
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:35 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped