Igor Pechtchanski wrote:
On Thu, 28 Jul 2005, Krzysztof Duleba wrote:
I am not. I understand that this is how it should work theoretically,
but I've _checked_ that on a couple of Cygwin boxes with different
versions of cygwin1.dll and gcc. All of them didn't really care that
heap_chunk_in_mb wa
> That's not good enough for scripting.
An expectation of complete congruence Unix <> Cygwin seems unrealistically
high to me. I've got a few scripts incorporating a branch as follows
#! /bin/sh
if [ -d c:/ ]
then
{Cygwin stuff}
else
{Unix equiv
Krzysztof Duleba wrote:
Igor Pechtchanski wrote:
Actually, you're right. Perhaps it depends on what kind of malloc the
program uses (i.e., whether it uses the Cygwin builtin malloc, or
something else).
That's strange. How could Perl use something essentially different than
malloc? I thought
Gerrit P. Haase wrote:
Krzysztof Duleba wrote:
Igor Pechtchanski wrote:
Actually, you're right. Perhaps it depends on what kind of malloc the
program uses (i.e., whether it uses the Cygwin builtin malloc, or
something else).
That's strange. How could Perl use something essentially differ
Gerrit P. Haase wrote:
Gerrit P. Haase wrote:
Krzysztof Duleba wrote:
Igor Pechtchanski wrote:
Actually, you're right. Perhaps it depends on what kind of malloc the
program uses (i.e., whether it uses the Cygwin builtin malloc, or
something else).
That's strange. How could Perl use so
Alex Goldman wrote:
When Cygwin gets set up, it would be more user-friendly if it placed
two icons on the desktop:
one should start maximized Rxvt; another should start X with a couple
of xterms or whatever.
First-time users might think that the MS-DOS terminal is as good as it
gets, and this is
Chris January wrote:
Alex Goldman wrote:
When Cygwin gets set up, it would be more user-friendly if it placed
two icons on the desktop:
one should start maximized Rxvt; another should start X with a couple
of xterms or whatever.
First-time users might think that the MS-DOS terminal is as goo
> -Original Message-
> From: Gerrit P. Haase [mailto:[EMAIL PROTECTED]
> Sent: 28 July 2005 00:26
> To: Oliver Walsh
> Cc: cygwin@cygwin.com
> Subject: Re: GConf2 and clear fork bomb on x64
>
> Oliver Walsh wrote:
>
> > Hi all,
> >
> > On Windows Server 2003 64bit, clear.exe and gconftool
Oliver Walsh wrote:
tried to run rebaseall?
?
There is no error, it fork bombs ie I get 4000 gconftool-2 processes.
strace doesn't output anything
The same with clear? Interesting ;)
Would you please attach the output of cygcheck -svr?
Gerrit
--
=^..^=
--
Unsubscribe info: http
Doug,
Please keep your replies on-list.
On Wed, Jul 27, 2005 at 05:16:06PM -0400, Doug Philips wrote:
> On Wednesday, July 27, 2005, at 04:50PM, Jason Tishler indited:
> >Either restored the symlink or change the trigger line to:
> >
> >#!/bin/ash
>
> Huh?
Sorry, my information is a little
On Wed, Jul 27, 2005 at 09:52:40PM +, Eric Blake wrote:
> > The sleep gave the sh.exe process time to exit. You "fixed" it but
> > in an open-loop way that is still prone to failure.
>
> Why not patch rebaseall to invoke 'grep -E' instead of 'egrep'?
Yes. Just to be safe, I'll take care of
Doug,
On Wed, Jul 27, 2005 at 10:38:44PM -0400, Douglas Philips wrote:
> On Jul 27, 2005, at 7:29 PM, Christopher Faylor wrote:
> >semaphore::_trywait doesn't have anything to do with pthread
> >mutexes, AFAIK.
>
> I don't know. When I saw the Python message it seemed plausible.
>
> The real i
On Wed, Jul 27, 2005 at 06:45:29PM -0400, Igor Pechtchanski wrote:
> No bug. It *is* a script (at least in binary tarball of grep). I
> don't know where Jason's symlink came from.
An older grep package.
> Jason, is your "grep" package up-to-date?
No.
Jason
--
PGP/GPG Key: http://www.tishler
I'm moving from a very technical slot to a unix manager slot.
I have done the tech thing for so long I know how to find answers
and put solutions together to make things work. I'm seeking everyone's
opinion on getting a laptop for this new slot. The laptop would
run windoze (must communication with
On Jul 28, 2005, at 8:48 AM, Jason Tishler wrote:
Doug,
I don't know. When I saw the Python message it seemed plausible.
The real issue is that Python broke with 1.5.18, either because of
the pthread change or not.
Be that as it may, should I report this bug in another forum?
No, this is th
On Thu, 28 Jul 2005, Ken Dibble wrote:
> Chris January wrote:
>
> > Alex Goldman wrote:
> >
> > > When Cygwin gets set up, it would be more user-friendly if it placed
> > > two icons on the desktop:
> > > one should start maximized Rxvt; another should start X with a
> > > couple of xterms or what
Original Message
>From: Ken Dibble
>Sent: 28 July 2005 11:48
> Checking to see if a new version available assumes an internet connection.
> My opinion is that this would play havoc with dial-up users.
Besides, who wants cygwin to phone home? That's waaay too much like
windoze!
> If t
Original Message
>From: Krzysztof Duleba
>Sent: 28 July 2005 08:00
> Igor Pechtchanski wrote:
>> On Thu, 28 Jul 2005, Krzysztof Duleba wrote:
>>
>>> I am not. I understand that this is how it should work theoretically,
>>> but I've _checked_ that on a couple of Cygwin boxes with different
On Thu, 28 Jul 2005, Douglas Philips wrote:
> On Jul 28, 2005, at 8:48 AM, Jason Tishler wrote:
>
> > Doug,
> > > I don't know. When I saw the Python message it seemed plausible.
> > >
> > > The real issue is that Python broke with 1.5.18, either because of
> > > the pthread change or not.
> > > B
Igor Pechtchanski wrote:
On Thu, 28 Jul 2005, Ken Dibble wrote:
Chris January wrote:
Alex Goldman wrote:
When Cygwin gets set up, it would be more user-friendly if it placed
two icons on the desktop:
one should start maximized Rxvt; another should start X with a
couple of
> -Original Message-
> From: Gerrit P. Haase [mailto:[EMAIL PROTECTED]
> Sent: 28 July 2005 13:31
> To: Oliver Walsh
> Cc: cygwin@cygwin.com
> Subject: Re: GConf2 and clear fork bomb on x64
>
> Oliver Walsh wrote:
>
> >>tried to run rebaseall?
>
> ?
>
>
> > There is no error, it fork b
New News:
===
I have updated the version of rebase to 2.4.2-1. The tarballs should be
available on a Cygwin mirror near you shortly.
The only notable change (to rebaseall) since the previous release is:
* Change zcat to "gzip -d -c" and egrep to "grep -E" to avoid the
possibility
On Thu, 28 Jul 2005, Dave Korn wrote:
> Original Message
> >From: Krzysztof Duleba
> >Sent: 28 July 2005 08:00
>
> > Igor Pechtchanski wrote:
> >> On Thu, 28 Jul 2005, Krzysztof Duleba wrote:
> >>
> >>> I am not. I understand that this is how it should work
> >>> theoretically, but I've _c
Original Message
>From: Igor Pechtchanski
>Sent: 28 July 2005 14:58
> Hmm, but shouldn't this code fail regardless of the value of
> heap_chunk_in_mb? Why does increasing heap_chunk_in_mb make this succeed?
Perhaps it only makes it succeed if you increase heap_chunk_in_mb until
that
The 'id' command indicates user staffuser1 is in group ABC_NA-CTX-Notepad-A.
I use this account 'staffuser1', and have no idea what group
ABC_NA-CTX-Notepad-A
is; I do not think user staffuser1 is really in that group, but you could
prove me wrong (how?).
This is causing problems in ssh session
At 09:13 AM 7/28/2005, Mike wrote:
>I'm moving from a very technical slot to a unix manager slot.
>I have done the tech thing for so long I know how to find answers
>and put solutions together to make things work. I'm seeking everyone's
>opinion on getting a laptop for this new slot. The laptop wou
On Thu, 28 Jul 2005, Dave Korn wrote:
> Original Message
> >From: Igor Pechtchanski
> >Sent: 28 July 2005 14:58
>
> > Hmm, but shouldn't this code fail regardless of the value of
> > heap_chunk_in_mb? Why does increasing heap_chunk_in_mb make this
> > succeed?
>
> Perhaps it only makes
I am trying to get my current expect scripts to run with the latest
cygwin but am having problems with the cmd-prompt after issuing the
command above. After the "echo $?", the expected prompt is returned but
with white space before it. I've never seen this before on Windows or
Unix.
Example:
$ ec
Original Message
>From: Maloney, Michael
>Sent: 28 July 2005 17:56
>
> Example:
> $ echo $?
> 0
> $
>
> The prompt($) has a space before it
> Any help???
WJFFM. What do you see from "echo $? | od -c" ?
cheers,
DaveK
--
Can't think of a witty .sigline today
--
$ echo $? | od -c
000 0 \n
002
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Dave Korn
Sent: Thursday, July 28, 2005 1:03 PM
To: cygwin@cygwin.com
Subject: RE: echo $?
Original Message
>From: Maloney, Michael
>Sent: 28 July 2005 1
Tom Rodman wrote:
> The 'id' command indicates user staffuser1 is in group ABC_NA-CTX-Notepad-A.
> I use this account 'staffuser1', and have no idea what group
> ABC_NA-CTX-Notepad-A
> is; I do not think user staffuser1 is really in that group, but you could
> prove me wrong (how?).
>
> This is
> I am trying to get my current expect scripts to run with the latest
> cygwin but am having problems with the cmd-prompt after issuing the
> command above. After the "echo $?", the expected prompt is returned but
> with white space before it. I've never seen this before on Windows or
> Unix.
>
W
>
> C:\>sh -i
> sh-3.00$ PS1="$ "
>
> I also noticed in version 1.5.17 that when executing the shell, the
> default prompt changed from "$ " to "sh-3.00$ ".
It wasn't the cygwin upgrade, but the bash upgrade that changed
your prompt. /bin/sh used to be ash, which defaults to PS1 of '$ ',
but is
Well, For now I just copied an old version of sh in. Is this going to be
fixed in future builds? I have the same issue with the .18 build as
well.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Eric Blake
Sent: Thursday, July 28, 2005 2:04 PM
To: Malo
Ugh - top-posting. Reformatted.
>
> > Well, bash-3.0-7 has a known display bug, and bash-3.0-8 requires
> > cygwin-1.5.18 or newer, so it might help. But your cygcheck.out
> > shows some other problems. First, in Windows, you have SHELL
> > defined as c:\MKS\mksnt\sh.exe, which is NOT the cygwi
Thank you again Pierre.
I appreciate the increased rights ;->It fixed up more than
just the net drive issue, a couple of my database admin commands that were
failing, now work again in an ssh session.
see comments below
--
regards,
Tom
On Thu 7/28/05 13:22 EDT "Pierre A. Humblet" wrote:
> T
Christopher Faylor wrote:
>>> semaphore::_trywait doesn't have anything to do with pthread
>>> mutexes, AFAIK.
Douglas Philips wrote:
>> The real issue is that Python broke with 1.5.18, either because of
>> the pthread change or not. Be that as it may, should I report this
>> bug in another forum?
Dave,
Some comments on your analysis.
The latest perl uses auto-image-base and the base address should be
different than default. It fails anyway.
Perl uses its own malloc, rebuilding with the system malloc shows
that it behaves similar than the C examples, I think the recent
changes in Cygw
Christopher Faylor wrote:
According to Alex Goldman on 7/21/2005 2:49 AM:
On Linux, after I start a program that consumes 100% of CPU time, I can
usually terminate it just by typing Ctrl-C. This is very convenient to
me as a developer. However, using Cygwin in the same situation, the
shell
On Fri, Jul 29, 2005 at 12:16:42AM +0200, Gerrit P. Haase wrote:
>Dave,
>
>Some comments on your analysis.
>
>The latest perl uses auto-image-base and the base address should be
>different than default. It fails anyway.
>
>Perl uses its own malloc, rebuilding with the system malloc shows
>that it
On Jul 28, 2005, at 9:49 AM, Igor Pechtchanski wrote:
That's why I culled down my large application to a small Python
script
which exhibited the bug and which I submitted to the list, along
with my
cygcheck -srv and the error messages that Python gave me.
So your test case is currently a sm
On Jul 28, 2005, at 6:02 PM, Williams, Gerald S (Jerry) wrote:
On the other hand, I verified at the time that the semaphore
solution worked under Cygwin Python, so I wouldn't expect it
to be a problem even if the change just took place. However,
it could potentially help in isolating the problem.
On 7/27/05, Don Beusee wrote:
> That's not good enough for scripting. First of all, the command is not so
> simple (you have to grep -v grep also - so that the same script works on
> Unix systems) and if you have small PID number like 14, that will likely
> return lots of other processes (like 114
43 matches
Mail list logo
