On Wed, 12 Nov 2003, Dylan Cuthbert wrote:
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
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
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.
Hi Chris,
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.
But anyway, this is 100% repeatable on my machine over the course of a day;
try setting up a cronjob to run every hour that rsync's a gig or so of files
over the
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 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
and my son would have a telephone in his room.
Do you have a cordless phone? - Then your son has *already* had a phone
in his room!
If this technique was uniformly useful then we'd have peace in the
Middle East
Persistence has to be uniform, consistent, morally obvious, concretely
defined
This could explain my problems running rsync as a cronjob and having the
tasks hang for long periods of time (they do terminate eventually). Its a
real pain when I try and log out or shutdown, as windows can't seem to
forcibly terminate the tasks (because they are spawned by a SYSTEM
Thank you Bob Byrnes for this info and analysis. Perhaps it will result
in a solution to a long simmering problem. I use cygwin VERY
aggressively. A cron job launches a 20,000 line perl script (not
including CPAN modules by other authors) that does complex network
automation tasks via multiple
On Fri, Oct 31, 2003 at 12:44:54PM +0900, Dylan Cuthbert wrote:
This could explain my problems running rsync as a cronjob
I don't remember you mentioning that you were sending large amounts of
data over a pipe before.
The only time this is a problem is when the pipe is full.
And, yes, it is a
On Thu, Oct 30, 2003 at 11:14:36PM -0500, Brian Kelly wrote:
Thank you Bob Byrnes for this info and analysis. Perhaps it will
result in a solution to a long simmering problem. I use cygwin VERY
aggressively. A cron job launches a 20,000 line perl script (not
including CPAN modules by other
] On Behalf
Of Christopher Faylor
Sent: Thursday, October 30, 2003 11:36 PM
To: [EMAIL PROTECTED]
Subject: Re: cygwin deadlocks due to broken select() when writing to
pipes
On Thu, Oct 30, 2003 at 11:14:36PM -0500, Brian Kelly wrote:
Thank you Bob Byrnes for this info and analysis. Perhaps it will
result
On Fri, Oct 31, 2003 at 12:59:17AM -0500, Brian Kelly wrote:
Nevertheless, a few persistent reminders over a long period can have
the same effect as a very large number of complaints in close
proximity.
There was once a great story in the Reader's Digest I think of some
prisoner somewhere who
13 matches
Mail list logo
