Guy Harris
changed
bug 11546
| What |
Removed |
Added |
| Status |
UNCONFIRMED
|
CONFIRMED
|
| Hardware |
x86-64
|
All
|
| Summary |
Files shown in welcome screen are polled permanently and captured in WireShark as SMB2
|
Files shown in welcome screen are checked every 2 seconds - causing network traffic if they're on a server
|
| Ever confirmed |
|
1
|
| OS |
Windows 7
|
All
|
Comment # 1
on bug 11546
from Guy Harris
Generic problem; there's nothing SMB2, or even SMB-in-general, specific about
it.
This is the same issue as the one in
https://ask.wireshark.org/questions/45036/permanent-smb2-traffic-with-1997
and I reproduced that - without the network accesses, as the capture files are
all local, but with periodic file system accesses - on OS X.
As is said there, Qt Wireshark checks every two seconds to make sure that the
files in the recent list are still there:
recent_timer_.setParent(this);
connect(&recent_timer_, SIGNAL(timeout()), this, SLOT(refreshRecentFiles()));
recent_timer_.start(2000);
in WiresharkApplication::WiresharkApplication() in
ui/qt/wireshark_application.cpp.
The comment before WiresharkApplication::refreshRecentFiles() says:
// Check each recent item in a separate thread so that we don't hang while
// calling stat(). This is called periodically because files and entire
// volumes can disappear and reappear at any time.
The good news is that, at least in some OSes, you can ask for notifications if
a file is removed or if the list of mounted volumes changed.
The bad news is that the way you do that is OS-dependent, and it might not be
doable on all OSes.
On Windows, OS X, Linux, and FreeBSD, there are ways we can arrange to get
notifications of file removal/renaming and unmounts, so we can at least do
better for Wireshark on those platforms.
See the long comment I added to ui/qt/wireshark_application.cpp, discussing the
use of QFileSystemWatcher to catch changes.
You are receiving this mail because:
- You are watching all bug changes.