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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5875B7F6.8090406@tlinx.org>
Date: Tue, 10 Jan 2017 20:43:34 -0800
From: L A Walsh <cygwin@tlinx.org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: hang on 'cat /proc/mounts' when one of the network drives is on a 'down' system
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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