X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; q=dns; s=default; b=Dmy
	0zWjebcVe+LQE6taP5ShcHrsjXaGnjU1SXxwLa2X4VUpuzFF0WIVANggpcMkPdZE
	LfJzkUC/cEgGbF0BcsB7hOR9FQR/vIITp2EPxEZXDjf86u4HY7zniej4a9GnAlDA
	YEW6UspEB2Mx5eU9RKcVn44d3Fqk5cGkpREPf3UI=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; s=default; bh=LVBehOqu1
	N+7UrW8thrZqtVApfo=; b=j5CTQnmYqVc6GAp0JNm081MAhUDwtGbcjXLMRjhPU
	jTdFaDUfeS7riVn9TZIZgshzbzJAzuEi++O72DGZKGp+p/qR97SwD7lBaWZeLCiA
	VD6NbpuqX848YUpL/BiqiA2syJ7rWTCu4SPAd07mE8YwAqU7BMTNXKOhAgS1flIb
	7M=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-3.2 required=5.0 tests=BAYES_40,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=1-2, H*F:U*cygwin, drives, exchange
X-HELO:	Ishtar.sc.tlinx.org
Message-ID:	<5875B7F6.8090406@tlinx.org>
Date:	Tue, 10 Jan 2017 20:43:34 -0800
From:	L A Walsh <cygwin AT tlinx DOT org>
User-Agent:	Thunderbird
MIME-Version:	1.0
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	hang on 'cat /proc/mounts' when one of the network drives is on a 'down' system
X-IsSubscribed:	yes

I noticed my local terminals were not opening w/a shell prompt, but
would timeout if I waited long enough...(1-2 minutes? maybe?).

Turns out, one of my mounted net-drives was a down-system, so
if I was trying to access the drive (or content on it), I can see
it hanging.

But what about "cat /proc/mounts" which is dumping out text
like:

Z: /z ntfs binary,user,noumount,auto 1 1

should require accessing and hanging for a few minutes?
Is it determining the network file type?  Wouldn't that
remain constant for a given session (like I doubt that
ntfs would exchange with smbfs and go back on fixed IP
machines).

I've tried using 'timeout', but it doesn't seem to work:

read -t proc_mounts < <(timeout -k 2 1 cat /proc/mounts)

(still hangs)

tnx,
-l






--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -