I've got nss-mysql installed and working except when you log on and it checks your user name and password it then goes and checks just about every gid. This is like 5000 sql calls to the database... It freezes for about 2 minutes after it displays the motd (after you log in) then works fine after that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I ran into this problem as well, and I found that the latest version out of the CVS did not do this.
I don't think the sorted version in the CVS has been released yet, but if you are using the latest release version, and this is still happening, then that must be the case.
So:
- If you're using the latest version, take the latest version out of CVS and it will work ok (it's been working fine on my server for *months* now!)
- If you're not using the latest version, try that, and if that does not fix it, then use the latest CVS version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've got nss-mysql installed and working except when you log on and it checks your user name and password it then goes and checks just about every gid. This is like 5000 sql calls to the database... It freezes for about 2 minutes after it displays the motd (after you log in) then works fine after that.
What's in your /etc/profile, .profile, or whatever your login scripts are? Maybe some program is polling all groups in there...
Nothin that seems pertinant:
# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
PATH="/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games"
if [ "$BASH" ]; then
PS1='\u@\h:\w\$ '
else
if [ "`id -u`" -eq 0 ]; then
PS1='# '
else
PS1='$ '
fi
fi
export PATH PS1
umask 022
I ran into this problem as well, and I found that the latest version out of the CVS did not do this.
I don't think the sorted version in the CVS has been released yet, but if you are using the latest release version, and this is still happening, then that must be the case.
So:
- If you're using the latest version, take the latest version out of CVS and it will work ok (it's been working fine on my server for *months* now!)
- If you're not using the latest version, try that, and if that does not fix it, then use the latest CVS version.