Controls/gitea-pages
0
2
Fork 0
Code Pull Requests Actions Activity

improved titles

Browse Source
This commit is contained in:
buchel_k
2023-10-19 15:47:43 +02:00
parent 489d6efbc7
commit 25675214e8
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
admin-guide/troubleshooting/pam.md
+2 -2
View File
@@ -3,7 +3,7 @@
Checking PAM issues can be quite tricky.
# Debugging Messages with `pam_echo.so`
## Debugging Messages with `pam_echo.so`
This can be used to print a message. When placed on every PAM step it shows how far the processing goes and maybe where the error might be:
@@ -38,7 +38,7 @@ auth optional pam_echo.so "Have passed pam_localuser and pam_unix"
```
# PAM Call Stack with SystemTap
## PAM Call Stack with SystemTap
When debugging an PAM issue with the RedHat support, they provided us a neat Systemtab script to create a PAM call stack of the `do_pam_setcred()` function in sshd. You find it [here](pam/para-callgraph-pam.stp).