Wireshark-dev: Re: [Wireshark-dev] slow startup caused by splash_update?
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>
Date: Mon, 06 Apr 2009 10:48:35 -0400


Jeremy Linton wrote:

Jeff Morriss wrote:

How are you accessing the system where you're running Wireshark?  ssh?
It is a LAN connection, but its not over SSH. The machine wireshark is running on is a vmware guest. It's a little on the slow side, but generally unusable. 

Once Wireshark is up, is it usable [going to Gerald's suggestion]?
Maybe Wireshark can/should disable the splash screen when run over ssh? ssh doesn't imply a slow connection but it's probably reasonably common.
Maybe any kind of network startup should have the splash updating scaled back. Although at this point I guess most remote X traffic does flow over SSH. I guess you can detect remote connections via GdkDisplay->use_xshm or XShmQueryExtension(), detecting if they are SSH is probably a little harder.
Actually detecting ssh shouldn't be too hard: when you ssh somewhere your shell gets some environment variables from ssh.