Message-Id: <200604022059.k32KxqtK001046@tigris.pounder.sol.net>
From: cygwin AT trodman DOT com (Tom Rodman)
Reply-to: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: ls displays nothing - 3/29 snapshot
In-reply-to: <20060402204331.GA8710@trixie.casa.cgf.cx>
References: <200604021937 DOT k32JbMHL000678 AT tigris DOT pounder DOT sol DOT net> <20060402204331 DOT GA8710 AT trixie DOT casa DOT cgf DOT cx>
Date: Sun, 02 Apr 2006 15:59:52 -0500
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Sun 4/2/06 16:43 EDT cygwin AT cygwin DOT com wrote:
> On Sun, Apr 02, 2006 at 02:37:22PM -0500, Tom Rodman wrote:
> >I installed the 3/29 cygwin1.dll snapshot yesterday on a test windows
> >2000 box.  Many (all?) of our cron jobs ran normally Sunday morning.
> >Today, though, the output of 'ls' or 'ls -l' from an interactive bash
> >session was always nothing.  I've reverted back to the released
> >cygwin1.dll, and ls is working again.
> >
> >Sorry for lack of details; not sure at what point the problem started
> >showing up.
> 
> That's ok.  Minus any details, we'll just assume that you've done
> something wrong and ignore the problem.

I have a scroll log of all the shell commands I did on Sat/Sun, and
logs from the cron jobs. Will post if I find anything helpful - so far
nothing out of the ordinary shows up in STDERR; I'll go over the logs
again ..

--
Tom

--
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/