After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 47942 - with an NFS-mounted home directory, the search for trash makes Nautilus unusable
with an NFS-mounted home directory, the search for trash makes Nautilus unusable
Status: VERIFIED INCOMPLETE
Product: nautilus
Classification: Core
Component: Trash
1.0.x
Other Linux
: Normal normal
: old
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-03-30 16:39 UTC by Sri Ramkrishna
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sri Ramkrishna 2001-09-10 01:19:50 UTC
This may already filed, and I know it's a known problem.
filing it anyways. :-)

My problem is that on large corporate environments nautilus causes a
major performance problem as it's start searching all over the place
for trash folders and to populate it's folder tree.

What I propose though is to be able to limit the search path based either
on compile time options by a system administrator and possibly have the
user be able to override the search options.  The current behavior seems
to be to start at the / and work it's way down.

This would really help able to deploy nautilus in large corporate environment.
Currently, GNOME 1.4 will not be able to be deployed in our current builds
at work because of this problem.

Thanks
sri



------- Additional Comments From darin@bentspoon.com 2001-03-30 12:13:03 ----

If the "populate its folder tree" remark is also correct, we should make a
separate bug report about that.



------- Additional Comments From don@eazel.com 2001-04-11 14:20:18 ----

Good idea.  But not for 1.0.3.




------- Additional Comments From snickell@stanford.edu 2001-07-23 00:33:02 ----

Taking bugs previously assigned to Pavel, assigning them to myself. Will parse
them out at my leisure , but many are GnomeVFS bugs we should look at for 2.0



------- Additional Comments From snickell@stanford.edu 2001-07-23 00:42:40 ----

Sri, can you please confirm that this is still a problem with 1.0.4? It seems to
work OK in the Xerox PARC NIS environment, but that is obviously not
representitive of every single NFS setup in the world.



------- Additional Comments From mjs@noisehavoc.org 2001-07-23 01:16:45 ----

Move to unassigned. I'll probably want to take a crack at some of these myself,
and Seth says he is unlikely to.




------- Additional Comments From sri@aracnet.com 2001-07-23 14:55:02 ----

Sure, I'll check.  I've been running it for awhile and it's a lot better.
I think we can close this issue out for now.  There are slowness problems but
I need to give you data to really figure out whats causing the slowness on
NFS mounted home dirs. 

    sri



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:19 -------
Comment 1 John Fleck 2002-01-05 04:21:03 UTC
Changing to "old" target milestone for all bugs laying around with no milestone set.
Comment 2 Sebastien Bacher 2003-11-25 18:15:34 UTC
No news on this bug for almost 2 years, could you test if the problem
is still here with nautilus 2.4 ?

Thanks
Comment 3 Matthew Gatto 2004-11-04 04:35:14 UTC
No news, closing.