Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: "Dylan Cuthbert" Subject: Re: cygwin deadlocks due to broken select() when writing to pipes Date: Wed, 12 Nov 2003 11:29:21 +0900 Lines: 90 Message-ID: References: <20031031033119 DOT 611A4E55A AT carnage DOT curl DOT com> <20031031042355 DOT GA23231 AT redhat DOT com> <20031102194147 DOT GA15320 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Ok, well it wasn't 100% cured with the TTY flag removed but it stopped it being a 100% daily problem to an "every other day or so" problem (depends on the direction of the wind I think). Why does TTY affect the behaviour of rsync and cron jobs? Also, this may be a silly question, but why does it try to kill my cron jobs when I log off from my user? Shouldn't they be running no matter what user is logged in, and regardless of whether I log in or log off? They definitely shouldn't be killed or need to be killed. --------------------------------- Q-Games, Dylan Cuthbert. http://www.q-games.com "Dylan Cuthbert" wrote in message news:bo9l4h$cq7$1 AT sea DOT gmane DOT org... > Ok, removing tty from the CYGWIN variable allows me to log off and shutdown > now. > > Why does the tty flag cause this kind of lock-up behaviour? Is there any > reason I need the tty flag at all? If not I'll just leave it off > permanently. > > --------------------------------- > Q-Games, Dylan Cuthbert. > http://www.q-games.com > > > "Dylan Cuthbert" wrote in message > news:bo4g20$v72$1 AT sea DOT gmane DOT org... > > CYGWIN=tty is on in the system env vars, shall I switch it off, is this > bad? > > I switched it on before I had this problem mind you, but maybe something > in > > the post-Sept-19th version mixes badly with CYGWIN=tty? > > > > Yes, I understand the "root of the problem" problem (sic.), ie. the > > programming law that there will always be a lot more causes than there are > > distinct effects. ;-) > > > > Anyway, I have this daily recurring problem, which seems to me to be > > duplicatible, yet no-one has tried to duplicate it yet? This is why I > > repeat the description of my problem wherever I can; in the daft hope > > someone will set up something similar and see if they get the same thing. > > I'm not doing anything complicated, just 2 or 3 rsync's (of half a gig or > > so) in a cronjob every two hours to a linux server. > > > > Regards > > > > --------------------------------- > > Q-Games, Dylan Cuthbert. > > http://www.q-games.com > > > > "Christopher Faylor" wrote in > > message news:20031102194147 DOT GA15320 AT redhat DOT com... > > > On Mon, Nov 03, 2003 at 12:29:53AM +0900, Dylan Cuthbert wrote: > > > >Actually I think I did mention I was running rsync hourly in a cron > job, > > > >that's all I've been mentioning as far as I know. > > > > > > Which has nothing to do with selecting on pipes unless (and even this is > > > pretty remote) you have turned on CYGWIN=tty for your cron for some > > > reason. > > > > > > The point that I am vainly trying to make is that if one person reports > > > a symptom like "hanging" and another person reports a symptom like > > > "hanging" in a completely different scenario while offering a rationale > > > for the behavior, it does not automatically mean that person B has found > > > the root cause for person A's problem unless person A and person B's > > > situations are the same. There is nothing in your (repeated) > description > > > of your problem to indicate that is the case. > > > > > > > > > > > > -- 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/