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