X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fyaz-log-man.xml;h=367712baaffdc0319c9d054d433222d4a06ea9a8;hb=323805b6779bcf1befdc7cdd7f10c23b06885e0d;hp=151097726790a2c5b57aed09cbe8681b742631c2;hpb=d940392c53c32ccf76fb287cc5b997b9e921a431;p=yaz-moved-to-github.git
diff --git a/doc/yaz-log-man.xml b/doc/yaz-log-man.xml
index 1510977..367712b 100644
--- a/doc/yaz-log-man.xml
+++ b/doc/yaz-log-man.xml
@@ -1,6 +1,6 @@
-
%local;
@@ -12,18 +12,20 @@
YAZ&version;
+ Index Data
-
+
yaz-log7
+ Conventions and miscellaneous
-
+
yaz-logLog handling in all yaz-based programs
-
+
yaz-XXXX
@@ -31,7 +33,7 @@
-
+
DESCRIPTION
All YAZ-based programs use a common log subsystem, and should support
@@ -41,9 +43,9 @@
-
+
OPTIONS
-
+
-l logfile
@@ -53,7 +55,7 @@
stderr is used. The log is appended to this file.
If the file grows overly large, it is silently rotated: It is renamed to
logfile.1,
- logfile.2, .., 9
+ logfile.2, .., 9
(old such file is deleted), and a
new file is opened. The limit defaults to 1GB, but can be set by the
program.
@@ -86,7 +88,7 @@
LOG LEVELS TO CONTROL LOGGING
- Some of the log levels control the way the log is written.
+ Some of the log levels control the way the log is written.
flush causes the log to be flushed after every write.
@@ -100,8 +102,8 @@
intended for automatic test scripts, which should produce predictable log
files that are easy to compare.
-
-
+
+ GENERAL LOG LEVELS IN YAZ ITSELF
@@ -121,7 +123,7 @@
levels (see below).
- all turns on almost all hard-coded log levels.
+ all turns on almost all hard-coded log levels.
loglevel logs information about the log levels used by
@@ -133,28 +135,28 @@
is to grep for yaz_log_module_level in the source
code, as in
- find . -name '*.[ch]' -print |
- xargs grep yaz_log_module_level |
+ find . -name '*.[ch]' -print |
+ xargs grep yaz_log_module_level |
grep '"' |
- cut -d'"' -f2 |
- sort -u
+ cut -d'"' -f2 |
+ sort -u
- eventl, malloc,
+ eventl, malloc,
nmem, odr are used internally for
debugging yaz.
-
+
LOG LEVELS FOR CLIENTSzoom logs the calls to the zoom API, which may be useful
in debugging client applications.
-
+
LOG LEVELS FOR SERVERS
@@ -166,14 +168,14 @@
request logs a one-liner for each request (init, search,
- etc).
+ etc.).
requestdetail logs the details of every request, before
it is passed to the back-end, and the results received from it.
- Each server program (zebra, etc) is supposed to define its own log levels
+ Each server program (zebra, etc.) is supposed to define its own log levels
in addition to these. As they depend on the server in question, they can
not be described here. See above how to find out about them.
@@ -229,23 +231,23 @@
14:45:41-23/11 yaz-ztest [requestdetail] Request to pack 1+1 1
14:45:41-23/11 yaz-ztest [requestdetail] pms=1048576, mrs=1048576
14:45:41-23/11 yaz-ztest [request] Present: [1] 1+1 OK 1 records returned
-
+
-
+
LOG FILENAME EXAMPLES
- A file with format my_YYYYMMDD.log is where Y, M, D is year, month, and day
- digits is given as follows
+ A file with format my_YYYYMMDD.log (where Y, M, D is year, month, and day
+ digits) is given as follows:
-l my_%Y%m%d.log . And since the filename
- is depending on day, rotaion will occur on midnight.
+ is depending on day, rotation will occur on midnight.
- A weekly log could be specified as
+ A weekly log could be specified as
-l my_%Y%U.log.
-
+
FILESprefix/include/yaz/log.h
@@ -279,15 +281,7 @@