r4653: Output file of "test" pdb backend should be called test.so

[ira/wip.git] / examples / pdb / README

diff --git a/examples/pdb/README b/examples/pdb/README
index 9ca03bf59388227da10b53cc9dd218706ca37eb0..baceb8e6009c2cec0229577923da2f7d497d429d 100644 (file)
--- a/examples/pdb/README
+++ b/examples/pdb/README
@@ -1,15 +1,16 @@
 README for Samba Password Database (PDB) examples
 ====================================================
-15-2-2002 Jelmer Vernooij <jelmer@nl.linux.org>
+Jelmer Vernooij <jelmer@nl.linux.org>
+Stefan (metze) Metzmacher <metze@samba.org>
 
-The pdb_test.c file in this directory contains a very basic example of 
+The test.c file in this directory contains a very basic example of 
 a pdb plugin. It just prints the name of the function that is executed using
 DEBUG. Maybe it's nice to include some of the arguments to the function in the 
 future too..
 
-To debug passdb backends, try to run gdb on the 'pdbedit' executable. That's really much easier than restarting smbd constantly and attaching with your debugger.
-
-New passdb plugins should go into the samba lib directory, (/usr/lib/samba/ for
-most distributions) and should be prefixed with 'pdb_'. An example would be: 
-/usr/lib/samba/pdb_test.so
+To debug passdb backends, try to run gdb on the 'pdbedit' executable. That's
+really much easier than restarting smbd constantly and attaching with your 
+debugger.
 
+New passdb plugins should go into the samba lib directory, (/usr/lib/samba/pdb/
+for most distributions). An example would be: /usr/lib/samba/pdb/test.so