LXDE clients joined to a DC running samba with a separate file server running smbd. All 12.3 Hi I'm trying to debug slow LXDE clients. One thing we've noticed is that the file server is flooded with smbd errors looking for files which don't exist e.g.: [2013/08/24 22:59:33.060232, 3] ../source3/smbd/trans2.c:5399(call_trans2qfilepathinfo) call_trans2qfilepathinfo: SMB_VFS_LSTAT of lynn2/.kde failed (No such file or directory) There are countless other file failures. These continue to be sent until I log out. If I log into the same account with KDE, win xp or win7 , the messages disappear and the file server reverts to inactivity after the initial burst of getting either my home folder or my windows profile. If I log into LXDE on a client which does not have KDE, the messages are still present. Following log.smbd and top is scary with the latter around 0.7% per client. That's unacceptable load in a domain. We've (almost) eliminated the DC as it runs its own version of smbd. The file server is a bare bones install and no one is logged in anyway. A Lubuntu client also behaves as expected. 1, Why is LXDE sending constant requests for files that don't exist? 2. What is the equivalent to log.smbd if I log in locally to a client? How do I see what files are being requested? (I need to totally eliminates cifs from this). Thanks, L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (1)
-
lynn