Skip to main content
Super User

Return to Answer

added 372 characters in body
Source Link
grawity_u1686
grawity_u1686
  • 465.3k
  • 66
  • 977
  • 1.1k

They are not cached by GNOME; the corresponding GVfs providers all take their data "live" from external sources. There are several sources that network:/// gets its data from – look at the internal GVfs path names to get hints:

gio list network:///

This will show the 'raw' item name, such as dnssd-something, and will reveal it as originating either from DNS-SD (aka Bonjour, aka mDNS, discovered via avahi-daemon) or from SMB (more accurately NetBIOS, discovered via Samba)... or perhaps from Google Cloud Print, which GNOME used to integrate with.

If the result is DNS-SD, the data was received from avahi-daemon, which has no persistent cache; any ghost entries should disappear after restarting the service. Try avahi-browse, or the graphical avahi-discover, and/or Wireshark or tcpdump to figure out what's producing the service advertisements. (Use the capture filter port 5353.)

They are not cached by GNOME; the corresponding GVfs providers all take their data "live" from external sources. There are several sources that network:/// gets its data from – look at the internal GVfs path names to get hints:

gio list network:///

This will show the 'raw' item name, such as dnssd-something, and will reveal it as originating either from DNS-SD (aka Bonjour, discovered via avahi-daemon) or from SMB (more accurately NetBIOS, discovered via Samba)... or perhaps from Google Cloud Print, which GNOME used to integrate with.

They are not cached by GNOME; the corresponding GVfs providers all take their data "live" from external sources. There are several sources that network:/// gets its data from – look at the internal GVfs path names to get hints:

gio list network:///

This will show the 'raw' item name, such as dnssd-something, and will reveal it as originating either from DNS-SD (aka Bonjour, aka mDNS, discovered via avahi-daemon) or from SMB (more accurately NetBIOS, discovered via Samba)... or perhaps from Google Cloud Print, which GNOME used to integrate with.

If the result is DNS-SD, the data was received from avahi-daemon, which has no persistent cache; any ghost entries should disappear after restarting the service. Try avahi-browse, or the graphical avahi-discover, and/or Wireshark or tcpdump to figure out what's producing the service advertisements. (Use the capture filter port 5353.)

Source Link
grawity_u1686
grawity_u1686
  • 465.3k
  • 66
  • 977
  • 1.1k

They are not cached by GNOME; the corresponding GVfs providers all take their data "live" from external sources. There are several sources that network:/// gets its data from – look at the internal GVfs path names to get hints:

gio list network:///

This will show the 'raw' item name, such as dnssd-something, and will reveal it as originating either from DNS-SD (aka Bonjour, discovered via avahi-daemon) or from SMB (more accurately NetBIOS, discovered via Samba)... or perhaps from Google Cloud Print, which GNOME used to integrate with.