summaryrefslogtreecommitdiffstats
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
commit765d87838dbf25ba69dc11f7956ce5814555bcc7 (patch)
treee87a8d59284210268696ffeb40f6decfbf48e4b3
parent280d627adb5305e8b814102aaa73825023c00571 (diff)
downloadsamba-765d87838dbf25ba69dc11f7956ce5814555bcc7.tar.gz
samba-765d87838dbf25ba69dc11f7956ce5814555bcc7.tar.xz
samba-765d87838dbf25ba69dc11f7956ce5814555bcc7.zip
Update for new modules system
-rw-r--r--examples/pdb/README9
1 files changed, 5 insertions, 4 deletions
diff --git a/examples/pdb/README b/examples/pdb/README
index 7fe45248824..c18e128e782 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