https://bugzilla.novell.com/show_bug.cgi?id=416415 Summary: Konqueror very slowly scans indirect mounts on an autofs Product: openSUSE 11.0 Version: Final Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers@suse.de ReportedBy: ccox@endlessnow.com QAContact: qa@suse.de Found By: Customer In 10.2, konqueror didn't attempt to resolve directories underneath an automount indirect directory. This is arguably correct behavior, though confusing to some. This is the behavior of cd and an ls from the shell. In 10.3 konqueror attempts to list all possible mount points (which could be HUGE btw) underneath an indirect mount point. The purpose of an indirect mount point it to mount directories under autofs as NEEDED. Konqueror makes the wrong assumption and proceeds to locate all possible mount points that might be found underneath the indirect mount directory. In 11.0, the behavior is like 10.3, except it does so VERY VERY VERY VERY slowly. Even in 10.3 you'll get errors for NFS mounts under the indirect point for which there are no permissions, but 11.0 it can take many many minutes. During that time, the whole KDE desktop is LOCKED up. The "right" behavior is to do what was done in 10.2. For example if your indirect autofs mount dir is called /shr, going to /shr by itself should reveal NOTHING. It's only when you go to /shr/remote-dir, that a mount of the NFS area is attempted and the mount happens via the autmounter. Right now, konqueror tries to find all possible indirecty mounts and MOUNT them (at a huge cost). I would love to see the behavior reverted to the way 10.2 behaves... which is what the shell does and is what is SUPPOSED to happen with indirect mounts underneath the automounter. You have to be explicit in order to force the mount. -- 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.