Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <41AE1451.1060006@x-ray.at>
Date: Wed, 01 Dec 2004 19:58:25 +0100
From: Reini Urban <rurban AT x-ray DOT at>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a4) Gecko/20040927
MIME-Version: 1.0
To: David Hinds <dhinds AT sonic DOT net>
CC: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: A vexing installation problem
References: <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129135305 DOT 046bca10 AT pop DOT prospeed DOT net> <20041129195946 DOT GA4932 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129151309 DOT 046bfba0 AT pop DOT prospeed DOT net> <20041129215220 DOT GA15085 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129171109 DOT 046d1728 AT pop DOT prospeed DOT net> <20041129231740 DOT GA32760 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129181904 DOT 046bf960 AT pop DOT prospeed DOT net> <20041130011421 DOT GA20359 AT sonic DOT net> <20041130170757 DOT GA3861 AT sonic DOT net> <20041130192952 DOT GA2722 AT sonic DOT net> <20041201184434 DOT GA7909 AT sonic DOT net>
In-Reply-To: <20041201184434.GA7909@sonic.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

David Hinds schrieb:
> Drat... Windows Update decided to install a "critical security fix"
> last night, and today, Cygwin appears to be 100% dead in the water as
> opposed to yesterday's 90%.  The security fix is supposed to be in
> Internet Explorer so it might just be a coincidence.
> 
> I've attached "strace" output from running "ls".  The output is
> slightly different from previous attempts, because I'd been able to
> run the postinstall scripts to populate /etc/passwd and /etc/group;
> but the failure mode appears unchanged, with death following shortly
> after signals are enabled.  The trace is still slightly variable from
> one run to the next; sometimes I get one or two messages about locks,
> sometimes not.
> 
> By the way, this is a dual Xeon workstation, without hyperthreading.

...

>   218   22778 [main] ls 1336 path_conv::check: this->path(\\duckling\dhinds), has_acls(0)
>   158   22936 [main] ls 1336 win_env::add_cache: posix //duckling/dhinds
>   149   23085 [main] ls 1336 win_env::add_cache: native HOME=\\duckling\dhinds
>   641   23726 [main] ls 1336 sigproc_init: process/signal handling enabled(1001)
>   203   23929 [main] ls 1336 __cygwin_lock_lock: threadcount 1.  not locking

And you really think using a UNC path $HOME is a good idea?
And you really think you must send us this strace just for telling us 
that cygwin didn't like your UNC path $HOME?
How about mounting this to a local volume
("net use * \\duckling\dhinds" or cygwin's mount)
Or better use a local drive for home instead?
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

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