Lukas Ocilka wrote:
Lukas Ocilka wrote:
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.
We've also found this kind of entries: Measure -> Measure.cc -> 5 Count: 103 Size: 12878
Maybe I should have told you more about the reason why minimized logging is worth investing your time. Installation of SUSE/openSUSE Linux needs quite a lot of memory because it uses virtual system (in memory) also for logging. Very often no swap is activated until the disk is formatted and installation really starts. YaST logs are not rotated during the installation and compression on-the-fly also seems to be very uneasy. So, all logs are stored in the uncompressed textual form. During upgrade, when there are several repositories available, the log sometimes take take tenths or even hundreds of megabytes. I'd like to point out some issues how logging could be optimized. Quite easy seems to be remove duplicated data stored into the log. See this example: --- example --- Source.cc(ScanProductsWithCallBacks):75 Scanning products in ftp://10.10.0.100/install/SLP/openSUSE-10.3-Build936-DVD/i386/DVD1 ... MediaAccess.cc(open):109 Trying scheme 'ftp' MediaCurl.cc(MediaCurl):177 MediaCurl::MediaCurl(ftp://10.10.0.100/install/SLP/openSUSE-10.3-Build936-DVD/i386/DVD1,) MediaAccess.cc(open):141 Opened: ftp(ftp://10.10.0.100/install/SLP/openSUSE-10.3-Build936-DVD/i386/DVD1 not attached; localRoot "") MediaManager.cc(open):426 Opened new media access using id 1 to ftp://10.10.0.100/install/SLP/openSUSE-10.3-Build936-DVD/i386/DVD1 --- example --- What's wrong there? The very same URL is logged four-times even if it would be enough to log it only once or twice. We don't use several threads so it's easy to track the URL in log-lines above. And even if we used several threads, there is always a PID written into the log. Please, try to remove such issues from the libzypp code. Thanks Lukas