fix(network): list NFS traffic on the drawer's network pageHEADmaster

A pcmanfm-qt copy of 8GB from an NFS share never appeared among the
busiest processes. The copy's bytes travel on the kernel NFS client's
TCP socket to port 2049, which ss reports with no users:(()) owner, and
sockets() skipped every ownerless socket. The file manager itself owns
no socket for the transfer at all.

Ownerless sockets whose peer port is 2049 are now kept and named
"NFS <server>". Which process drives the traffic is not knowable from
ss, so the row names the share's server instead. Other ownerless
sockets (other users', without root) are still skipped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions