I am very grateful to Ben for coding this project. I am worried because everything seems to be getting so out-of-date
here on the website. I find the whole project so useful that I'd like to help out if I can, so I created some new
documentation to get the latest version of libnss-mysql up and working.
I wrote this documentation because on 11/30/07, I tried installing libnss-mysql using the documentation from
the sourceforge website and found that the code for the project had be updated, but the documentation and examples had not.
It is my hope that I can save you the numerous hours it took me to get the new version up and running.
About 2 years ago I implemented libnss-mysql for one of my customers using FreeBSD. My customer is still running
the original configuration on an updated FreeBSD 6.3pre box without any issues. I am concerned that at some point
in the future that an update will completely break his setup. He currently has 500+ accounts setup in MySQL and from my
current experiences in setting up the new version, a migration will involve quite a bit of work.
The new box that I configured is an up-to-date Ubuntu 7.10 Gutsy server running version 1.0-4 of libnss-mysql and
libpam-mysql version 0.6.2-1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The examples and documentation included in my project should work perfectly. I'll certainly fix that if that's not the case -- but I'll need pointers to what's inaccurate.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well that would certainly explain things. I apologize. Please feel free to delete my post so that no one gets confused. When I did an apt-cache search for nss-mysql, the only packages that come up are for the other project. That's really too confusing with the names being so similar. I thought I was helping you guys out. Sorry.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can find all of my config files and a complete readme at -
http://dfwlinuxguy.com/libnss-mysql/
I am very grateful to Ben for coding this project. I am worried because everything seems to be getting so out-of-date
here on the website. I find the whole project so useful that I'd like to help out if I can, so I created some new
documentation to get the latest version of libnss-mysql up and working.
I wrote this documentation because on 11/30/07, I tried installing libnss-mysql using the documentation from
the sourceforge website and found that the code for the project had be updated, but the documentation and examples had not.
It is my hope that I can save you the numerous hours it took me to get the new version up and running.
About 2 years ago I implemented libnss-mysql for one of my customers using FreeBSD. My customer is still running
the original configuration on an updated FreeBSD 6.3pre box without any issues. I am concerned that at some point
in the future that an update will completely break his setup. He currently has 500+ accounts setup in MySQL and from my
current experiences in setting up the new version, a migration will involve quite a bit of work.
The new box that I configured is an up-to-date Ubuntu 7.10 Gutsy server running version 1.0-4 of libnss-mysql and
libpam-mysql version 0.6.2-1
Based on this config file:
http://dfwlinuxguy.com/libnss-mysql/nss-mysql.conf
You're not using this project's code. You're using http://savannah.nongnu.org/projects/nss-mysql/
Is that the reason for the confusion?
The examples and documentation included in my project should work perfectly. I'll certainly fix that if that's not the case -- but I'll need pointers to what's inaccurate.
Well that would certainly explain things. I apologize. Please feel free to delete my post so that no one gets confused. When I did an apt-cache search for nss-mysql, the only packages that come up are for the other project. That's really too confusing with the names being so similar. I thought I was helping you guys out. Sorry.