[Pvfs2-cvs] commit by vilayann in pvfs2/doc: pvfs2-quickstart.tex
CVS commit program
cvs at parl.clemson.edu
Thu Aug 10 15:02:20 EDT 2006
Update of /anoncvs/pvfs2/doc
In directory parlweb1:/tmp/cvs-serv12929/doc
Modified Files:
pvfs2-quickstart.tex
Log Message:
Gossip'ized kmod as well so that we dont have 2 separate calls to printing diagnostics.
gossip for the kmod is fairly primitive and is handled simply by means of a macro in gossip.h.
Replaced and removed pvfs2_print and pvfs2_error with gossip_debug.
Edited quickstart to include comments on the new kmod debug parameters as well.
Index: pvfs2-quickstart.tex
===================================================================
RCS file: /anoncvs/pvfs2/doc/pvfs2-quickstart.tex,v
diff -p -u -r1.38 -r1.39
--- pvfs2-quickstart.tex 19 Apr 2006 19:22:58 -0000 1.38
+++ pvfs2-quickstart.tex 10 Aug 2006 19:02:20 -0000 1.39
@@ -937,7 +937,15 @@ variable to a valid file name. This cau
specified by the PVFS2\_DEBUGMASK to be stored in the file specified,
no longer intermixing the output with the client program. The file
specified in the PVFS2\_DEBUGFILE environment variable will be
-appended if it already exists.
+appended if it already exists.
+Another influential environment variable that can be used to trigger
+kmod logging messages is PVFS2\_KMODMASK. By setting values of this variable
+to ``file, inode'' prior to starting pvfs2-client-core daemon,
+verbose kmod subsystem error diagnostics are written to the system ring buffer
+and eventually to the kernel logs.
+One could also set the kmod diagnostic level when the kernel module is loaded
+like so, insmod pvfs2.ko gossip\_debug\_mask=<diagnostic level>.
+The diagnostic level will be a bitwise OR of values specified in pvfs2-debug.h.
\section{ROMIO Support}
\label{sec:romio}
More information about the Pvfs2-cvs
mailing list