On Mar 2 14:20, Frank Fesevur wrote:
> 2014-02-28 22:08 GMT+01:00 Corinna Vinschen:
> > That's not really a problem but a case of "it is as it is". To get the
> > user and group info, Cygwin has to contact the DC and/or GC and then
> > runs into a timeout. Right now, the LDAP timeout is set to 3
On Mar 1 02:08, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> > I've just uploaded a new snapshot to http://cygwin.com/snapshots/
>
> I've sent a reply with testing details, but it may have been caught by SPAM
> deflection for "excess use of foreign language".
> Please disregard this no
2014-03-03 10:21 GMT+01:00 Corinna Vinschen:
> No, this is not mintty's fault. You have to understand that the
> request for information from the DC is called before the actual
> application had any chance to initialize, This happens before
> the application has, in fact, been called from the Cyg
Frank Fesevur writes:
> 2014-03-03 10:21 GMT+01:00 Corinna Vinschen:
>> - We allow the user to specify a timeout value and set the default to
>> 1 second.
> I think the [above] makes most sense. Maybe even keep the default
> timeout on 3 seconds. When the user can change the value, it is up to
Hi,
cygwin64 shares for 64-bit the ABI of Windows native. This is caused
by different reasons (eg. unwind-table description for prologue, etc).
So for Windows targets va_list is indeed of 'char *' type. And this
is ok. The variant of x86_64 abi, which uses indeed a
structure-variant for variadi
On Mar 3 12:29, Henry S. Thompson wrote:
> Frank Fesevur writes:
>
> > 2014-03-03 10:21 GMT+01:00 Corinna Vinschen:
> >> - We allow the user to specify a timeout value and set the default to
> >> 1 second.
>
> > I think the [above] makes most sense. Maybe even keep the default
> > timeout on 3
On 2/26/2014 5:07 AM, Corinna Vinschen wrote:
Weird, I was pretty sure we already have an /etc/shells file installed
by default. Apparently not. So, shan't we add one?
/bin/sh
/bin/bash
/bin/dash
/bin/mksh
/bin/zsh
/usr/bin/sh
/usr/bin/bash
/usr/bin/dash
/usr/bin/mks
The following packages have been added to the Cygwin distribution:
* google-breakpad-tools
* google-breakpad-devel
google-breakpad is a multi-platform crash reporting and analysis system using
minidumps.
The google-breakpad-tools package contains the minidump_dump and
minidump_stackwalk tools f
Greetings, Corinna Vinschen!
>> > I've just uploaded a new snapshot to http://cygwin.com/snapshots/
>>
>> I've sent a reply with testing details, but it may have been caught by SPAM
>> deflection for "excess use of foreign language".
>> Please disregard this notification, if a message will finall
On Mar 2 12:20, Ken Brown wrote:
> On 2/21/2014 10:32 AM, Angelo Graziosi wrote:
> >Trying to build libsigsegv-2.10 on Cygwin64 (using the src tarball and
> >its .cygport file from x86 distribution), fails as follows
> >
> >[...]
> >libtool: compile: gcc -DHAVE_CONFIG_H -I.
> >-I/works/tmp/libsig
Greetings, Charles Wilson!
> Speaking of base-files, version 4.1-2 has been in test now for over two
> years...works fine here and fixes a problem with $TEMP and other
> "standard" variable names: 4.1-1 set both $TEMP and $temp, but these are
> not distinguished by native processes, leading to c
On Mar 3 08:55, Charles Wilson wrote:
> On 2/26/2014 5:07 AM, Corinna Vinschen wrote:
> >Weird, I was pretty sure we already have an /etc/shells file installed
> >by default. Apparently not. So, shan't we add one?
> >
> > /bin/sh
> > /bin/bash
> > /bin/dash
> > /bin/mksh
> > /bin/zsh
>
On Mar 3 18:47, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> > I've just uploaded a new snapshot to http://cygwin.com/snapshots/
> >>
> >> I've sent a reply with testing details, but it may have been caught by SPAM
> >> deflection for "excess use of foreign language".
> >> Please di
Would it be possible to have an aspell-it dictionary added to Cygwin64?
I remember that in the past someone prepared that package (at least for
Cygwin32) and flagged it to the Cygwin lists, but the request was lost...
TIA,
Angelo.
--
Problem reports: http://cygwin.com/problems.html
FA
Hmm, I think that stuff around EXCEPTION_DEBUG_EVENT is that what you
are searching for. See for some details
http://msdn.microsoft.com/en-us/library/windows/desktop/ms679299%28v=vs.85%29.aspx
Regards,
Kai
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cy
Greetings, Corinna Vinschen!
>> In the meantime, I see my previous mail was indeed caught in the middle. I'll
>> repost it with a link to test results.
> Nah, never mind. I'm more interested of your experiences than in
> dry numbers :)
Oh, don't be so quick, lady...
The results were quite inter
On Mar 3 16:15, Kai Tietz wrote:
> Hmm, I think that stuff around EXCEPTION_DEBUG_EVENT is that what you
> are searching for. See for some details
> http://msdn.microsoft.com/en-us/library/windows/desktop/ms679299%28v=vs.85%29.aspx
These are functions for the debugger. I was looking for a way t
On Mar 3 16:14, Angelo Graziosi wrote:
> Would it be possible to have an aspell-it dictionary added to Cygwin64?
>
> I remember that in the past someone prepared that package (at least
> for Cygwin32) and flagged it to the Cygwin lists, but the request
> was lost...
You could volunteer to mainta
Greetings, Corinna Vinschen!
> No, this is not mintty's fault. You have to understand that the
> request for information from the DC is called before the actual
> application had any chance to initialize, This happens before
> the application has, in fact, been called from the Cygwin DLL.
> The
On Mar 3 16:02, Corinna Vinschen wrote:
> On Mar 2 12:20, Ken Brown wrote:
> [...]
> > I found the problem (or at least I found *a* problem): There's a
> > configure test "checking whether a fault handler according to POSIX
> > works", which passes on 32-bit Cygwin but fails on 64-bit Cygwin.
>
> On Mar 2 14:20, Frank Fesevur wrote:
> > 2014-02-28 22:08 GMT+01:00 Corinna Vinschen:
> > > That's not really a problem but a case of "it is as it is". To get the
> > > user and group info, Cygwin has to contact the DC and/or GC and then
> > > runs into a timeout. Right now, the LDAP timeout
On 3/3/2014 12:06 PM, Corinna Vinschen wrote:
On Mar 3 16:02, Corinna Vinschen wrote:
On Mar 2 12:20, Ken Brown wrote:
[...]
I found the problem (or at least I found *a* problem): There's a
configure test "checking whether a fault handler according to POSIX
works", which passes on 32-bit Cyg
Greetings, Corinna Vinschen!
>> I'd need to test it in domain environment, but I don't have access to one
>> with
>> Cygwin installed right now. Or, perhaps, I do?... let me check something.
> Sure.
I just thought of a derelict pair of virtualbox containers, that were set up
to simulate domain
Greetings, Corinna Vinschen!
>> I'd need to test it in domain environment,
And with sane number of groups (less than 20), the results are barely
different between different caching strategies (less than 1%, which could
easily be explained by measurement error), except (again) for the case of
runi
(Please note the date of the quoted emails)
On Mon, May 23, 2005 at 07:58:01PM -0700, Yitzchak Scott-Thoennes wrote:
> On Mon, May 23, 2005 at 06:34:21PM +0430, Alireza Ghasemi wrote:
> > Hello,
> > I have downloaded some c++ libraries and tried to download them.But All of
> > them give an error l
On Mon, Mar 3, 2014 at 1:47 PM, Kai Tietz wrote:
> Hi,
>
> cygwin64 shares for 64-bit the ABI of Windows native. This is caused
> by different reasons (eg. unwind-table description for prologue, etc).
> So for Windows targets va_list is indeed of 'char *' type. And this
> is ok. The variant of x
On 3/3/2014 08:52, Andrey Repin wrote:
I'd say it again, "sane defaults are better, than alot of options".
Agreed in principle.
However, observe that all network stacks have a bunch of built-in
timeout options. They're rarely exposed to the user level, but their
defaults are typically quit
Greetings, Warren Young!
>> I'd say it again, "sane defaults are better, than alot of options".
> Agreed in principle.
> However, observe that all network stacks have a bunch of built-in
> timeout options. They're rarely exposed to the user level, but their
> defaults are typically quite high
On 3/3/2014 18:36, Andrey Repin wrote:
Once TCP session is established, it remains,
until closed or dropped on either end of the wire.
Have you done the packet capture to prove that Windows does in fact keep
the LDAP connection to the AD server up continually, or are you making
an assumption?
29 matches
Mail list logo
