[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]]

[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]

[[!tag open_issue_glibc open_issue_hurd open_issue_porting]]


# IRC, freenode, #hurd, 2012-12-06

    <braunr> we need a netstat command
    <pinotree> wouldn't that require rpcs and notifications in pfinet to get
      info on the known sockets?
    <braunr> depends on the interface
    <braunr> netstat currently uses /proc/net/* so that's out of the question
    <braunr> but a bsd netstat using ioctls could do the job
    <braunr> i'm not sure if it's done that way
    <braunr> i don't see why it would require notifications though
    <pinotree> if add such rpcs to pfinet, you could show the sockets in procfs
    <braunr> yes
    <braunr> that's the clean way :p
    <braunr> but why notifications ?
    <pinotree> to get changes on data of sockets (status change, i/o activity,
      etc)
    <pinotree> (possibly i'm forgetting some already there features to know
      that)
    <braunr> the socket state is centralized in pfinet
    <braunr> netstat polls it
    <braunr> (or asks it once)