On Fri, Mar 20, 2015 at 9:56 PM, Yaakov Selkowitz wrote:
> On Fri, 2015-03-20 at 15:03 +, Peter Hull wrote:
>> Is this expected/normal or have I done something wrong?
> This is not expected. Nothing depends on epiphany that would have
> caused it to be pulled in without having selected it (or
Rexdf writes:
> If I just use package from cygwin mirrors, I will get the following
> error. I rebased many times,it does not work.
>
> 0 [unknown (0x2F04)] python2.7 2144 child_copy: loaded dll data write
> copy failed, 0x36402000..0x36402044, done 0, windows pid 5768, Win32
> error 487
>
> The
I observed the same error. In my case, it was apparently caused by a too-rapid
startup at boot of cygserver, which apparently could not connect to LDAP at
that early stage. If I prevented any of my Cygwin services from starting at
boot, and then started them manually once I logged in, the prob
Hi David,
On Mar 21 13:50, Habermann, David (D) wrote:
> I observed the same error. In my case, it was apparently caused by a
> too-rapid startup at boot of cygserver, which apparently could not
> connect to LDAP at that early stage.
LDAP can't have to do with that, in theory. The whole mechani
On Mar 20 22:13, Mirko Vukovic wrote:
> Hello,
>
> after upgrading cygwin64 on my company laptop, mintty gives the following
> message *when connected to the network from home*:
>
> /sbin/nologin: No such file or directory
I replied to David's mail, but the same puzzled observations and
question
>LDAP can't have to do with that, in theory. The whole mechanism should give a
>sane result even if LDAP >connections fail, because the core part is the call
>to LookupAccountSid and that's the only call which has to >succeed.
Certainly my speculation of the cause is exactly thatspeculatio
6 matches
Mail list logo
