linux-kernel - Seeing TCP socket options (nodelay, cork, etc) in Linux procfs or elsewhere?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <5608FA8A997F1A46B7E985494F8478DD07930AF1@ELON17P32003A.csfb.cs-group.com>
Date:	Mon, 15 Mar 2010 15:49:50 -0000
From:	"MacCana, Mike" <mike.maccana@...dit-suisse.com>
To:	<linux-kernel@...r.kernel.org>
Subject: Seeing TCP socket options (nodelay, cork, etc) in Linux procfs or elsewhere?

Hi kernel folks,

I was wondering if there was a standard location to see TCP socket
options (eg, nodelay, cork, etc), perhaps via procfs or some other
means? I'd like to check whether arbitrary apps (for which I don't have
code) are using particular TCP options. 

Wandering round /proc/net hasn't turned up anything yet, and after a
quick:
socket.setsockopt(0, 1, 1)
to enable NODELAY I can't see any obvious difference in procfs or
netstat output (where other Unixes seem to put this info). hat's the
best way to see TCP options on sockets created by others' code?

Thanks,

Mike

Mike MacCana 
Engineer
RDO Low Latency Infrastructure 
CREDIT SUISSE
Phone: +44 (0)20 7883 5907 
Mobile: +44 (0)7547 004474 
mike.maccana@...dit-suisse.com  
Five Canada Square, London, E14 4QJ. 
www.credit-suisse.com 

=============================================================================== 
 Please access the attached hyperlink for an important electronic communications disclaimer: 
 http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html 
 =============================================================================== 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/