|
Bugzilla – Full Text Bug Listing |
| Summary: | SuSEconfig.kdm3 using excessive time | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Ruediger Oertel <ro> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
up to critical ... looks good to me besides the -f /etc/lilo.conf .. what about if /etc/lilo.conf is a symlink to one of a set of alternative lilo.conf configurations (the user could have set up something like that) ? perhaps -e or -r would be enough. -f follows the symlink - and Adrian checked in the patch and left the bug open (old habits never die) |
I times the usage of SuSEconfig modules on a multiple run (taking a bit of time on a firest run is tolerated, a rerun should better not be above 1 second). SuSEconfig.kdm3 has exactly one problem: Executing /sbin/conf.d/SuSEconfig.kdm3... real 0m20.443s user 0m0.036s sys 0m0.292s which is caused by "lilo -q". proposed fix: --- /sbin/conf.d/SuSEconfig.kdm3~ 2005-08-26 12:33:12.000000000 +0200 +++ /sbin/conf.d/SuSEconfig.kdm3 2005-08-26 12:33:21.000000000 +0200 @@ -148,7 +148,7 @@ fi LILOCMD="-e s/^UseLilo=.*/UseLilo=false/" -if test -x /sbin/lilo; then +if test -x /sbin/lilo -a -f /etc/lilo.conf ; then /sbin/lilo -q > /dev/null 2>&1 if test "$?" = 0; then LILOCMD="-e s/^UseLilo=.*/UseLilo=true/"