summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJelmer Vernooij <jelmer@samba.org>2003-04-28 01:21:28 +0000
committerJelmer Vernooij <jelmer@samba.org>2003-04-28 01:21:28 +0000
commit9b93eb6f82a349273b6e402d9623179785cadce1 (patch)
treee34bd9e498aab93995e1159ba97d0f71a2130b8f
parent616f6b6ffe6db63461f33ce398aa918bae632393 (diff)
downloadsamba-9b93eb6f82a349273b6e402d9623179785cadce1.tar.gz
samba-9b93eb6f82a349273b6e402d9623179785cadce1.tar.bz2
samba-9b93eb6f82a349273b6e402d9623179785cadce1.zip
Update for new modules system
(This used to be commit 765d87838dbf25ba69dc11f7956ce5814555bcc7)
-rw-r--r--examples/pdb/README9
1 files changed, 5 insertions, 4 deletions
diff --git a/examples/pdb/README b/examples/pdb/README
index 7fe4524882..c18e128e78 100644
--- a/examples/pdb/README
+++ b/examples/pdb/README
@@ -8,8 +8,9 @@ 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). An example would be: /usr/lib/samba/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