linux-kernel - Finding out socket/pipe connectivity status

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: <Pine.LNX.4.64.0708121059160.28963@fbirervta.pbzchgretzou.qr>
Date:	Sun, 12 Aug 2007 17:12:28 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: Finding out socket/pipe connectivity status

Hi,

when a pipe/socket is broken, the process trying to read/write to it 
gets SIGPIPE. Is there a way to detect whether the next read/write will 
trigger a SIGPIPE? select() does not seem helpful here.

My specific case is "ssh server svprogram", in which the ssh process is 
locally terminated with ^C, and the svprogram continues to run on the 
server (good so), and when a socket breaks, it should cleanly shut down -
ideally before the next read/write is attempted.

thanks,
	Jan
-- 
-
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/