www.delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <3134710.post@talk.nabble.com> |
Date: | Sun, 26 Feb 2006 09:49:41 -0800 (PST) |
From: | Lichtkind <webmaster AT domainspank DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | cygwin stack? problem |
MIME-Version: | 1.0 |
X-Nabble-Sender: | webmaster AT domainspank DOT com |
X-Nabble-From: | Lichtkind <webmaster AT domainspank DOT com> |
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 |
Hello, i have made a little bash script that is beeing looped for days (endless), but after some hours the script seems to bug.. seems like a stack problem or something. (or memory?). script just uses wget, grep, cat, sort, and other common bash commands.. nothing special. any idea why after hours the script starts to bug? it cant be script itself, i am sure about that. must be a cygwin problem somehow thanks -- View this message in context: http://www.nabble.com/cygwin-stack-problem-t1189670.html#a3134710 Sent from the Cygwin Users forum at Nabble.com. -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |