Greetings, Mike Brown!
>> Sorry that I can't help you with your cron problem, but have you
>> considered using the Windows Task Scheduler instead given the urgency of
>> your situation? It can be used to kick off Cygwin processes just like
>> any other. You'll need to wrap your existing tasks wi
Hello Jeremy,
Many thanks for your reply. To be sure, I was quite incredulous myself bash
would have problems with empty lines, but that's what happens for me.
To be precise:
- I'm running Win7-64, Home Premium SP1
- I built Cygwin by running setup.exe with all the default options. The bash
is
Dear Christopher,
PLEASE read the three posts (the second one in particular) in the thread
referenced below, and THEN decide who started the "rant". Thank you.
Merry Christmas,
Emanuel
Christopher Faylor-8 wrote:
>
> On Sat, Dec 17, 2011 at 12:21:40AM -0600, Jeremy Bopp wrote:
>>On 12/16/20
On 17/12/2011 15:50, manu0507 wrote:
> - the script causing trouble comes in the GNU gdb distribution
> gdb-7.3.1.tar.gz
Hah! I know what's happened: you used a windows program such as winzip or
similar to unpack the archive, and it's gone and "helpfully" munged all the
line endings for you.
On Sat, Dec 17, 2011 at 09:04:38AM -0500, Pierre A. Humblet wrote:
> cron logs to syslog, which by default uses the Windows log and which you
> can read directly in Windows or filter with cronevents.
Good to know for the future.
> It's the first time I can recall where this is a problem, except
On Sat, Dec 17, 2011 at 06:52:16PM +0400, Andrey Repin wrote:
> nnCron, then?
> http://nncron.ru/
> nnCron supports that, if memory not deceiving me.
As pointed out in a followup posting, I reverted back to version 1.5 and all
is working again.
MB
--
e-mail: vid...@vidiot.com | vid...@vidiot.net
On 12/17/11, Dave Korn wrote:
> On 17/12/2011 15:50, manu0507 wrote:
>
>> - the script causing trouble comes in the GNU gdb distribution
>> gdb-7.3.1.tar.gz
>
> Hah! I know what's happened: you used a windows program such as winzip or
> similar to unpack the archive, and it's gone and "helpfully
On Sat, Dec 17, 2011 at 12:16:02PM -0500, Pierre A. Humblet wrote:
> That's weird also because there is no uid 0 in the /etc/passwd you sent
> earlier.
You're right. I never even noticed that. Also explains why there wasn't a
user name associated with the UID. D'Oh!
> Could there be some confu
Hi Dave,
Dave Korn-9 wrote:
>
> On 17/12/2011 15:50, manu0507 wrote:
>
>> - the script causing trouble comes in the GNU gdb distribution
>> gdb-7.3.1.tar.gz
>
> Hah! I know what's happened: you used a windows program such as winzip
> or
> similar to unpack the archive, and it's gone and "h
On Sat, Dec 17, 2011 at 07:57:30AM -0800, manu0507 wrote:
>PLEASE read the three posts (the second one in particular) in the thread
>referenced below, and THEN decide who started the "rant". Thank you.
I did read Eric's reply (which is the only one which would have any
bearing). I know Eric. I k
On Sat, Dec 17, 2011 at 10:27:23AM -0800, manu0507 wrote:
> That being said, it's still sort of beyond me why all [CR][LF]s would be
> converted ok... except the ones I reported.
It isn't a smart comversion, it is a blind substitute all conversion.
MB
--
e-mail: vid...@vidiot.com | vid...@vidiot
Reini Urban wrote:
Thanks for the nice testcase. I'll try to take it upstream.
But I'm not too confident that p5p will fix it, e.g. they refused to
fix File::Copy::cp, keeping the perms as with /bin/cp for several
years.
I could recently fix the cygwin write check if you had admin rights though.
12 matches
Mail list logo
