diff options
| author | Lauri Aarnio <lauri.aarnio@iki.fi> | 2008-01-03 02:58:17 +0200 |
|---|---|---|
| committer | Lauri Leukkunen <lle@rahina.org> | 2008-01-03 18:16:32 +0200 |
| commit | 9be5627dfe209505744f081bd3aad7fcfd4012f9 (patch) | |
| tree | 8eac3a760301e31f34d0274949888aaa02966c0a /README | |
| parent | a7ff25c508d37a760c7248050929812887148be1 (diff) | |
Added log post-processing tool and improved logging messages.
- added sb2logz, which extracts information from logs and produces summaries
- general: log format changed (each line now contains log level, too)
- *.c: log messages which are needed by sb2logz are now at INFO level
- interface.master & libsb2.c: Added gates to _exit() and _Exit(),
so that exit status can be logged
- sb_exec.c: bugfix: sb_execve_mod() returns nonzero if error, not zero
- sb2: location of log files changed: logs now go to ~/sb2_logs/,
and initial environment is printed to the log file
Diffstat (limited to 'README')
| -rw-r--r-- | README | 30 |
1 files changed, 29 insertions, 1 deletions
@@ -1,7 +1,7 @@ SCRATCHBOX 2 README author: Lauri Leukkunen <lle@rahina.org> -date: 2007-12-14 +date: 2008-01-03 @@ -135,5 +135,33 @@ development work in $HOME/src. The "-d" switch is needed to skip checking build dependencies, this is one of the remaining TODO items of SB2. + +DIAGNOSING PROBLEMS WITH SB2 + +Sometimes everything does not work as expected, so it is good to know +how to locate problems (typically problems are related to misconfigured +mapping rules). Scratchbox 2 can produce extensive logs about all +operations, but it does not do so by default. So the first step is +to enable logging: Use the "-d" or "-L <level>" options of "sb2". + +For example, + +$ sb2 -L info dpkg-buildpackage -rfakeroot -d + +will produce a log of most important actions that were performed by +"dpkg-buildpackage" and all subprocesses started by it. The log will +be created under ~/sb2_logs/ (The above command will also print out the +exact name and location of the logfile.) + +The produced logfile can be quite huge, especially when using the higher +logging levels. A logfile analyzer script, sb2logz, can be used to extract +essentials like error and warning messages and path mapping actions from +the logged information; log level 'info' in enough for anything that +sb2logz needs. Higher logging levels ('debug', etc) are mostly useful +only for developers of scratchbox 2. + + + +-- That's all folks, enjoy! |