path: root/doc
diff options
authorAndrew G. Morgan <>2001-02-11 06:48:12 +0000
committerAndrew G. Morgan <>2001-02-11 06:48:12 +0000
commit7ca1d77e784cd9ba836c50998ba9f6ad67965b21 (patch)
treed45bea68c072d2e4b5c21b390b89864275428290 /doc
parent4e4d6bb78e3bd6430838d854832c58f104d5f559 (diff)
Relevant BUGIDs: 131192
Purpose of commit: documentation Commit summary: --------------- added some links to sample module code (into the CVS repository).
Diffstat (limited to 'doc')
1 files changed, 15 insertions, 6 deletions
diff --git a/doc/pam_modules.sgml b/doc/pam_modules.sgml
index 8afd01fa..6440b289 100644
--- a/doc/pam_modules.sgml
+++ b/doc/pam_modules.sgml
@@ -4,7 +4,7 @@
- Copyright (c) Andrew G. Morgan 1996-9. All rights reserved.
+ Copyright (c) Andrew G. Morgan 1996-2001. All rights reserved.
** some sections, in this document, were contributed by other
** authors. They carry individual copyrights.
@@ -49,7 +49,7 @@ DAMAGE.
<title>The Linux-PAM Module Writers' Guide
<author>Andrew G. Morgan, <tt></tt>
-<date>DRAFT v0.75 2001/02/04
+<date>DRAFT v0.75 2001/02/10
This manual documents what a programmer needs to know in order to
write a module that conforms to the <bf/Linux-PAM/ standard. It also
@@ -1294,13 +1294,22 @@ endif
For some further examples, see the <tt>modules</tt> subdirectory of
the current <bf/Linux-PAM/ distribution.
<sect>An example module file
-perhaps this should point to a place in the file structure!?
+At some point, we may include a fully commented example of a module in
+this document. For now, we point the reader to these two locations in
+the public CVS repository:
+<item> A module that always succeeds: <tt><htmlurl
+<item> A module that always fails: <tt><htmlurl