Changeset 1721
- Timestamp:
- 08/04/08 10:55:19 (5 months ago)
- Files:
-
- cherokee/trunk/doc/debug.txt (modified) (4 diffs)
- cherokee/trunk/doc/media/images/tracelor.png (added)
- cherokee/trunk/doc/modules_validators_ldap.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
cherokee/trunk/doc/debug.txt
r1647 r1721 22 22 ---- 23 23 24 * You can also enable a new cool feature: CHEROKEE_TRACE, which will let you trace the 25 behavior with a human-readable output: 24 * You can also enable a cool feature: the CHEROKEE_TRACE environment 25 variable to trace what is going on inside the server. To enable it 26 you must add a special flag to your `configure` or `autogen.sh` 27 statement: 26 28 27 29 ---- … … 29 31 ---- 30 32 31 Now, when you are going to launch the web server, just add the CHEROKEE_TRACE variable, 32 with the desired options: 33 This will let you trace the behavior with a human-readable output. 34 Now, when you are going to launch the web server, just add the 35 CHEROKEE_TRACE variable, with the desired options: 36 33 37 34 38 ---- … … 47 51 ---- 48 52 49 Of course, you can trace all the modules (handlers, loggers..) you need:53 Of course, you can trace all the modules (handlers, loggers..) you need: 50 54 51 55 ---- … … 54 58 ---- 55 59 60 By default the environment variable contains a list of comma separated 61 words, that point the server which parts and actions are interesting 62 for your trace. Besides, there are a few special cases: 63 64 - all: Activates all the trace points 65 - time: Prints the time at the beginning of the line 66 - thread: Prints the thread ID 67 68 * You can also access the functionality of CHEROKE_TRACE through 69 `cherokee-tweak`. Refer to the apropriate section of the 70 documentation to learn more about this: 71 link:bundle_cherokee-tweak.html[cherokee-tweak]. 72 73 * Lastly a utility is provided, `contrib/tracelor.py`, to provide 74 further help to these tracing abilities. It is a little script that 75 helps to read the tracing logs by colorizing the thread references 76 and highlighting the words passed through the command line. 77 78 And example of usage would be: 79 80 ---- 81 CHEROKEE_TRACE=thread,all ./cherokee | ../contrib/tracelor.py iocache 82 ---- 83 84 And it would yield an output such as the following. Even if it is 85 not rocket science, it's a handy script to trace the server more 86 easily. 87 88 image::media/images/tracelor.png[Output of tracelor.py] 89 90 91 cherokee/trunk/doc/modules_validators_ldap.txt
r1647 r1721 1 LDAP Validator 2 ~~~~~~~~~~~~~~ 3 The LDAP validator allows you to authenticate a user using the 4 Lightweight Directory Access Protocol v3. 5 6 Parameters 7 ^^^^^^^^^^ 8 9 [grid="rows"] 10 ``~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 11 Parameter , Description 12 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 13 __server__ , Name of the host providing the LDAP service. 14 __port__ , Optional. Port number of the LDAP service. \ 15 Default: __389__. 16 __binddn__ , Optional. Bind Distinguished Name (`user`). If none \ 17 is provided and anonymous bind will be attempted. 18 __bindpw__ , Bind Password (`password`). 19 __basedn__ , Base Distinguished Name. 20 __filter__ , A filter that defines the conditions that must be \ 21 fulfilled in order for the search to match a given \ 22 entry. 23 __tls__ , Optional. Enable the use of TLS based integrity. \ 24 Defaults to __0__. 25 __ca_file__ , Optional. It Certificate File. Must be provided \ 26 if TLS is enabled. 27 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 28 29 Compatibility 30 ^^^^^^^^^^^^^ 31 32 This validator is compatible with the **basic** scheme. 33 34 Example 35 ^^^^^^^ 36 To be written