public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stewart Midwinter <stewart.midwinter@gmail.com>
To: Michael Brand <cygwin@brand.scso.com>
Cc: cygwin@cygwin.com
Subject: Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1
Date: Tue, 14 Feb 2006 17:35:00 -0000	[thread overview]
Message-ID: <d4c0d4800602140904r1ce8afa9l51653af196d8adee@mail.gmail.com> (raw)
In-Reply-To: <43F174FF.1040102@brand.scso.com>

fyi..

---------- Forwarded message ----------
From: Michael Brand <cygwin@brand.scso.com>
Date: Feb 13, 2006 11:13 PM
Subject: Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1
To: Stewart Midwinter <stewart.midwinter@gmail.com>
Cc: cygwin@cygwin.com


 Nope, I never found a good solution, and suspect that a good solution
here requires patching some Cygwin internals, but here are three
workarounds we used back then:

 1. Disable one CPU.
 2. Use watchdog processes that will kickstart things if they get stuck.
 3. Switch to *much* older Cygwin versions, which seem to be free of
this problem.

 I am still hoping for a Cygwin version that fixes this, but I guess
that as long as there are so few people who, like me, use Cygwin as a
mass-processing infrastructure, there is little chance of this problem
getting to the top of the list of priorities.

 Cheers,
 M.


 Stewart Midwinter wrote:

 From: Michael Brand <cygwin <at> brand.scso.com>



 I disabled one of the CPUs on my dual-CPU Xeon, and everything started working

 well, so I guess this is a dual-cpu problem.



 I tried running my scripts on several dual-CPU Xeons (different
computer models, but all of them HPs), ... snip ...
it generally crashes an hour or two later, at the most.

 Joining the party a *little* late here ... :-)

I too have a dual-CPU Xeon made by HP and it too has a problem with a
tcsh script hanging when it runs for a long time (it's a polling
script). We suspect that it might have to do with forking, but are
unable to test that theory at this time.

Apart from disabling the 2nd CPU (which kind of defeats the purpose of
having such a machine!), did you ever find any other solution?

thanks
Stewart



--
Stewart Midwinter
stewart@midwinter.ca
stewart.midwinter@gmail.com
Skype, GoogleTalk, iChatAV, MSN, Yahoo: midtoad
AIM:midtoad1






--
Stewart Midwinter
stewart@midwinter.ca
stewart.midwinter@gmail.com
Skype, GoogleTalk, iChatAV, MSN, Yahoo: midtoad
AIM:midtoad1

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

  parent reply	other threads:[~2006-02-14 17:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 22:19 Stewart Midwinter
2006-02-14  1:33 ` Christopher Faylor
     [not found] ` <43F174FF.1040102@brand.scso.com>
2006-02-14 17:35   ` Stewart Midwinter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-04 13:53 Michael Brand
2004-03-04 17:25 ` Christopher Faylor
2004-02-25 19:14 Michael Brand
2004-02-25 20:57 ` Larry Hall
2004-02-24 19:46 Michael Brand
2004-02-23 14:25 Michael Brand
2004-02-23 15:59 ` Corinna Vinschen
2004-02-23 17:26 ` Michael Brand
2004-02-23 21:18   ` Larry Hall
2004-02-24 15:47     ` Michael Brand
2004-02-24 17:00       ` Michael Brand
2004-02-24 17:59         ` Michael Brand
2004-02-24 18:03         ` Christopher Faylor
2004-02-24 17:11       ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d4c0d4800602140904r1ce8afa9l51653af196d8adee@mail.gmail.com \
    --to=stewart.midwinter@gmail.com \
    --cc=cygwin@brand.scso.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).