This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: cygcheck calling id.exe with nontsec
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 24 Mar 2003 20:22:20 -0500
- Subject: Re: cygcheck calling id.exe with nontsec
- References: <3.0.5.32.20030324193705.007f0100@mail.attbi.com>
- Reply-to: cygwin at cygwin dot com
On Mon, Mar 24, 2003 at 07:37:05PM -0500, Pierre A. Humblet wrote:
>cygcheck calling id.exe with CYGWIN=nontsec has a problem...
At the risk of sounding ungrateful, can I point you at
http://cygwin.com/bugs.html?
The fact that you are reporting a problem in cygcheck doesn't mean that
the hints there are not still useful. It would hvae saved me some time
trying to puzzle out what you'd discovered if you'd 1) described it
and 2) included cygcheck output. I suspect that you may even have
figured out why the problem was happening. It certainly worked fine
for me the first time I tried cygcheck.
Anyway, I've checked in a fix for this. Thanks for the bug report.
cgf
>> id
>uid=11054(PHumblet) gid=12655(Clearusers) groups=11114(AEngineering),
> 12655(Clearusers),10513(Domain Users),11005(Engineering),
> 544(Administrators),545(Users)
>
>~> CYGWIN=nontsec id
>uid=11054(PHumblet) gid=12655(Clearusers) groups=
> 12060(Canon Color Copier),12655(Clearusers)
>
>~> cygcheck -s
><snip>
>e:\bin\id.exe output (nontsec) <==?????????????????????????
>UID: 11054(PHumblet) GID: 12655(Clearusers)
>11114(AEngineering) 12655(Clearusers)
>10513(Domain Users) 11005(Engineering)
>544(Administrators) 545(Users)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/