Mailinglist Archive: zypp-devel (92 mails)

[Lukas Ocilka <lukas.ocilka@xxxxxxx>]

Hi,

There are several bugreports in bugzilla that YaST logs are still
increasing and they're very often impossible to attach them into a
bugreport because of 5MB limit.

I wrote a simple script that goes through the file given as a parameter
and prints the output in this format:

Example
-------
Log line:
2007-08-27 10:32:48 <0> 10.10.103.73(3944) [parser::susetags]
RepoParser.cc(parse):424 ReferenceCounted(@0xb4656f70<=1)

Output:
$VAR1 = {
    'parser::susetags' => {
        'RepoParser.cc' => {
            '0' => {
                'count' => 1,
                'size' => 72,
            }
            ...
        }
        ...
    }
    ...
}

The script is not ideal but could provide some hints where to look and
which logs to remove or minimize.

Without any offense, the biggest 'sinner' ;) is libzypp.

I've used y2log-1 from bug #304815 as an example. The format is:
Source File | Log Level | Count | Total Size in Bytes

QueueItemRequire.cc 1 1956    285.556
                    0  450     88.196
ContextPool.cc      0 6145    844.020
Exception.cc        5 7807  1.531.198
Resolver.cc         1 6630    886.471
                    0 12858 1.664.251
MediaCurl.cc        0 5900    968.752
ResolverUpgrade.cc  1 15506 2.675.810
ExternalProgram.cc  0 7479  1.145.172

The log file has 15.601.918 bytes in total...
Entries mentioned above are just an example and I know that common
libzypp developer can find more information that I did in the output.

Both the script and the exemplary output have been attached.
Please, remove as much logs (mostly debugging entries) as you can.
Thanks

Lukas

-- 

Lukas Ocilka, YaST Developer                     (xn--luk-gla45d)
-----------------------------------------------------------------
SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic