From 5c463c80010e3fe3c7fd393bd47f807707045ef2 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Thu, 23 Sep 2004 06:21:24 +0000 Subject: Add more debugging information, both generic and for the VFS extd_audit module. (This used to be commit c1763e368c1152b8117d1934147a508b3b089316) --- docs/Samba-HOWTO-Collection/Bugs.xml | 46 ++++++++++++++++++++++++++++++++++++ docs/Samba-HOWTO-Collection/VFS.xml | 34 ++++++++++++++++++++++++++ 2 files changed, 80 insertions(+) (limited to 'docs/Samba-HOWTO-Collection') diff --git a/docs/Samba-HOWTO-Collection/Bugs.xml b/docs/Samba-HOWTO-Collection/Bugs.xml index 12f8055599..09b4899276 100644 --- a/docs/Samba-HOWTO-Collection/Bugs.xml +++ b/docs/Samba-HOWTO-Collection/Bugs.xml @@ -121,6 +121,52 @@ all bugs can be tracked at a setting of 10, but be prepared for a large volume of log data. + + Debugging Specific Operations + + + Samba-3.x permits debugging (logging) of specific functional components without unnecessarily + cluttering the log files with detailed logs for all operations. An example configuration to + achive this is shown in: + + + + +log level0 tdb:3 passdb:5 auth:4 vfs:2 +max log size0 +log file/var/log/samba/%U.%m.log + + + + + This will cause the level of detail to be expanded to the debug class (log level) passed to + each funtional area per the value shown above. The first value passed to the log level + of 0 means turn off all unnecessary debugging except the debug classes set for + the functional areas as specified. The table shown in Debugable Functions + may be used to affect very precise analysis of each SMB operation Samba is conducting. + + + + Debuggable Functions + + + Function NameFunction Name + + + allpassdb + tdbsam + printdriversauth + lanmanwinbind + smbvfs + rpc_parseidmap + rpc_srvquota + rpc_cliacls + + +
+ + + diff --git a/docs/Samba-HOWTO-Collection/VFS.xml b/docs/Samba-HOWTO-Collection/VFS.xml index d9030a5633..48770f5412 100644 --- a/docs/Samba-HOWTO-Collection/VFS.xml +++ b/docs/Samba-HOWTO-Collection/VFS.xml @@ -138,6 +138,40 @@ This can be done using a configuration similar to the one shown in + + Configuration of Auditing + + + This auditing tool is more felxible than most people readily will recognize. There are a number of ways + by which useful logging information can be recorded. + + + + Syslog can be used to record all transaction. This can be disabled by setting + in the &smb.conf; file syslog = 0. + Logging can take place to the default log file (log.smbd) + for all loaded VFS modules just be setting in the &smb.conf; file + log level = 0 vfs:x, where x is the log level. + This will disable general logging while activating all logging of VFS + module activity at the log level specified. + Detailed logging can be obtained per user, per client machine, etc. + This requires the above together with the creative use of the + log file settings. + An example of detailed per-user and per-machine logging can + be obtained by setting + log level + /var/log/samba/%U.%m.log. + + + + + Auditing information often must be preserved for a long time. So that the log files do not get rotated + it is essential that the max log size0 be set + in the &smb.conf; file. + + + + -- cgit