On Nov 25 20:22, Habermann, David (D) wrote:
> > Thanks. Unfortunately it's not useful, because the actual problem
> > occurred inside Cygserver. What I need would be the problem captured
> > by running cygserver from the command line like this:
>
> > $ strace -o cygserver.trace /usr/sbin/cygse
> Thanks. Unfortunately it's not useful, because the actual problem
> occurred inside Cygserver. What I need would be the problem captured
> by running cygserver from the command line like this:
> $ strace -o cygserver.trace /usr/sbin/cygserver -d 2> cygserver.stderr
Strace output attached. A
> Does this record have one or more entries in the sidHistory attribute?
Yes, as you suspected, the sidHistory attribute for
S-1-5-21-1060284298-861567501-682003330-76794 contains
S-1-5-21-4015118-2039090470-1726288727-4013
> That's a bit of a problem for debugging. Did you notice my mail
> https://cygwin.com/ml/cygwin/2014-11/msg00480.html, btw?
Just taking a step back...what are we trying to fix? Once startup goes
smoothly, your current AD code works fine for me. The only problem I'm having
is that sometimes s
On Nov 25 17:32, Habermann, David (D) wrote:
> On Nov 25 16:24, Habermann, David (D) wrote:
> > >> Still, some debugging on affected systems might be enlightening.
> >
> > > I'll be happy to do anything of interest. As a starter, I'm going
> > > to see if I can figure out which of my SIDs are be
On Nov 25 17:09, Habermann, David (D) wrote:
> > Two things to keep in mind:
>
> > - It's not actually clear yet if it's a sidHistory entry or some SID
> > created by another mechanism.
>
> > Even if it's sidHistory, it may be *very* old. Did you work at the
> > company already back in NT4 tim
On Nov 25 16:24, Habermann, David (D) wrote:
> >> Still, some debugging on affected systems might be enlightening.
>
> > I'll be happy to do anything of interest. As a starter, I'm going
> > to see if I can figure out which of my SIDs are being used by the
> > couple of file shares I routinely
> Two things to keep in mind:
> - It's not actually clear yet if it's a sidHistory entry or some SID
> created by another mechanism.
> Even if it's sidHistory, it may be *very* old. Did you work at the
> company already back in NT4 times? That might explain the sidHistory
> entry and the tot
On Nov 25 16:24, Habermann, David (D) wrote:
> >> Still, some debugging on affected systems might be enlightening.
>
> > I'll be happy to do anything of interest. As a starter, I'm going
> > to see if I can figure out which of my SIDs are being used by the
> > couple of file shares I routinely
>> Still, some debugging on affected systems might be enlightening.
> I'll be happy to do anything of interest. As a starter, I'm going
> to see if I can figure out which of my SIDs are being used by the
> couple of file shares I routinely access from cygwin.
I was unable to quickly figure out
> Thanks. Unfortunately it's not useful, becasue the actual problem
> occurred inside Cygserver. What I need would be the problem captured
> by running cygserver from the command line like this:
> $ strace -o cygserver.trace /usr/sbin/cygserver -d 2> cygserver.stderr
> and see the two files cy
On Nov 24 21:46, Habermann, David (D) wrote:
> > > Stopping the terminal and restarting cygserver is not sufficient?
> > > Also, does this also happen if you don't start cygserver at all?
> >
> > I've not tried either of these ... and I'm not sure if it happens at
> > every reboot now or not (I ra
> > Stopping the terminal and restarting cygserver is not sufficient?
> > Also, does this also happen if you don't start cygserver at all?
>
> I've not tried either of these ... and I'm not sure if it happens at
> every reboot now or not (I rarely reboot). I'll see if I can
> reproduce it.
>
> >
On Thu, Nov 20, 2014 at 4:48 AM, Corinna Vinschen wrote:
>
> Still, some debugging on affected systems might be enlightening.
While you're thinking/debugging don't forget about a thumb drive that
contains Cygwin and is moved from computer to computer; even in and
out of domains, home and back to
On Nov 18 17:54, Corinna Vinschen wrote:
> On Nov 18 16:26, Habermann, David (D) wrote:
> > From: cygwin-owner
> > The problem here is the abbreviation in both cases. What I was looking
> > for is if your user uid/SID shows up in the token group list as well.
> > I don't need the full list, but ca
>> I've not tried either of these ... and I'm not sure if it happens at
>> every reboot now or not (I rarely reboot). I'll see if I can
>> reproduce it.
>>
>> > When the problem occurs, can you provide an strace from id?
>> >
>> > $ strace -o id.trace /usr/bin/id
>>
>> Will do if I can get it t
On Nov 18 16:26, Habermann, David (D) wrote:
> From: cygwin-owner
> The problem here is the abbreviation in both cases. What I was looking
> for is if your user uid/SID shows up in the token group list as well.
> I don't need the full list, but can you please check?
>
> 1125370 does not occur any
-Original Message-
From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of
Corinna Vinschen
Sent: Tuesday, November 18, 2014 10:58 AM
To: cygwin@cygwin.com
Subject: Re: occasional failure to look up
On Nov 18 15:49, Habermann, David (D) wrote:
> > Do you logi
On Nov 18 15:49, Habermann, David (D) wrote:
> > Do you login with your Microsoft account?
>
> I am logged into my workstation using the id "DOW\U074036". Of course the
> services I mentioned to not run under my ID, but instead under "SYSTEM"
> (except sshd, which uses privsep)
>
> > Is 112537
> Do you login with your Microsoft account?
I am logged into my workstation using the id "DOW\U074036". Of course the
services I mentioned to not run under my ID, but instead under "SYSTEM" (except
sshd, which uses privsep)
> Is 1125370 your primary group id? Can you please paste the output o
On Nov 18 14:50, Habermann, David (D) wrote:
> I am using the AD-enabled cygwin test versions (v33-0.5), with nsswitch.conf
> setting to "db" only.
>
> Occasionally when starting a cygwin terminal after a reboot I find that it
> get the following message:
>
> /usr/bin/id: cannot find the name f
I am using the AD-enabled cygwin test versions (v33-0.5), with nsswitch.conf
setting to "db" only.
Occasionally when starting a cygwin terminal after a reboot I find that it get
the following message:
/usr/bin/id: cannot find the name for group ID 1125370
Note that this is not a group ID, but
22 matches
Mail list logo
