https://bugzilla.novell.com/show_bug.cgi?id=816390 https://bugzilla.novell.com/show_bug.cgi?id=816390#c0 Summary: Susefirewall2 increased boot time by 39 seconds for half a year after installation Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: zorki@softhome.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=536201) --> (http://bugzilla.novell.com/attachment.cgi?id=536201) Today boot chart User-Agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0 Six months ago, I installed OpenSuSe 12.2 with desktop xfce on an old office laptop (Samsung R40). After installing the boot time was 72 seconds (from pressing the power button until you have a desktop without hard disk activity). 8 seconds for initialization BIOS, 6 seconds for counter GRUB2. It can be said that the net boot time was 58 seconds. After six months of use boot time is 123 seconds. Of these, 8 seconds initialization BIOS, 6 seconds - counter GRUB2. It can be said that the net boot time today is 109 seconds. That is, six months use increased boot time (excluding BIOS initialization and GRUB2 counter) by 51 seconds. Analysis of the boot process with systemd-analyze showed that the boot time (shown in the boot chart - systemd-analyze plot) increased from 39 to 81 seconds. That is a difference of 42 seconds for six month use. Thus, a quick analysis showed that the boot time increased by 42 seconds by loading system directly (that displays the systemd-analyze) and 9 seconds by loading the desktop. A more detailed analysis of the boot charts immediately after installation and after six months showed that all the same (+-1 second) until the beginning of the initialization SuSeFirewall2-init.service, which was loaded on a fresh installation of 6 seconds, after six months of use - 39 seconds. In this case, network.service wait the end of the running SuSeFirewall2-init.service. In addition, the boot time of NetworkManager.service is increased from 5 to 45 seconds. However, it seems that the NetworkManager.service expects for running SuSeFirewall2-init.service, because after loading network.service NetworkManager.service loaded in 8 seconds (after a clean install was 5 seconds). It seems that the main culprit of increasing the boot time is SuSeFirewall2-init.service, boot time for SuSeFirewall2-init.service is increased by 32 seconds for six month of use. How to correct the behavior of SuSeFirewall2 during system boot and get back a normal boot time? Reproducible: Always Steps to Reproduce: 1. Install OpenSuSe 12.2 2. Use OpenSuSe 12.2 for six month 3. Your boot time increased approximately twice -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.